Source: python-django-registration Version: 2.2-5 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team <t...@security.debian.org> Control: found -1 2.2-2
Hi, The following vulnerability was published for python-django-registration. CVE-2021-21416[0]: | django-registration is a user registration package for Django. The | django-registration package provides tools for implementing user- | account registration flows in the Django web framework. In django- | registration prior to 3.1.2, the base user-account registration view | did not properly apply filters to sensitive data, with the result that | sensitive data could be included in error reports rather than removed | automatically by Django. Triggering this requires: A site is using | django-registration < 3.1.2, The site has detailed error reports | (such as Django's emailed error reports to site staff/developers) | enabled and a server-side error (HTTP 5xx) occurs during an attempt by | a user to register an account. Under these conditions, recipients of | the detailed error report will see all submitted data from the | account-registration attempt, which may include the user's proposed | credentials (such as a password). The code has moved around a bit between the version we have and newest upstream version, but the issue unless mistaken is present as well in 2.2. It is claimed indeed that it is before 3.1.2 upstream. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-21416 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21416 [1] https://github.com/ubernostrum/django-registration/security/advisories/GHSA-58c7-px5v-82hh [2] https://github.com/ubernostrum/django-registration/commit/8206af081e239598cfd15d165d4d8ab9849ee23c Regards, Salvatore
