CVE Vulnerabilities

CVE-2021-21416

Generation of Error Message Containing Sensitive Information

Published: Apr 01, 2021 | Modified: Nov 21, 2024
CVSS 3.x
2.6
LOW
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
CVSS 2.x
3.5 LOW
AV:N/AC:M/Au:S/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

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 Djangos 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 users proposed credentials (such as a password).

Weakness

The product generates an error message that includes sensitive information about its environment, users, or associated data.

Affected Software

Name Vendor Start Version End Version
Django-registration Django-registration_project * 3.1.2 (excluding)
Python-django-registration Ubuntu bionic *
Python-django-registration Ubuntu focal *
Python-django-registration Ubuntu groovy *
Python-django-registration Ubuntu hirsute *
Python-django-registration Ubuntu impish *
Python-django-registration Ubuntu kinetic *
Python-django-registration Ubuntu lunar *
Python-django-registration Ubuntu mantic *
Python-django-registration Ubuntu oracular *
Python-django-registration Ubuntu trusty *
Python-django-registration Ubuntu xenial *

Potential Mitigations

  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References