CVE-2024-45231: Django CVE-2024-45230 and CVE-2024-45231

Published Sep 3, 2024
·
Updated

An issue was discovered in Django v5.1.1, v5.0.9, and v4.2.16. The django.contrib.auth.forms.PasswordResetForm class, when used in a view implementing password reset flows, allows remote attackers to enumerate user e-mail addresses by sending password reset requests and observing the outcome (only when e-mail sending is consistently failing).

Other sources

Django could allow a remote attacker to obtain sensitive information, caused by unhandled email sending failures. By sending a specially crafted password reset request, an attacker could exploit this vulnerability to enumerate user email information, and use this information to launch further attacks against the affected system.

— IBM

Affected Software

16 affected componentsFixes available
pip/django<4.2.16
4.2.16
pip/django>=5.0<5.0.9
5.0.9
pip/django>=5.1<5.1.1
5.1.1
djangoproject Django>=4.2.0<4.2.16
djangoproject Django>=5.0<5.0.9
djangoproject Django=5.1
IBM Storage Defender - Resiliency Service<=2.0.0 - 2.0.9
debian/python-django<3:3.2.25-0+deb12u1
3:3.2.25-0+deb12u1
debian/python-django<3:4.2.16-1
3:4.2.16-1
debian/python-django<3:4.2.16-1
3:4.2.16-1
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
debian/python-django
3:3.2.25-0+deb12u33:3.2.25-0+deb12u63:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.17-23:5.2.19-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 4.2.16
  2. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.0.9
  3. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.1.1
  4. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u1
  5. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:4.2.16-1
  6. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 4.2.16-r0
  7. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u3Fixed in 3:3.2.25-0+deb12u6Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.17-2Fixed in 3:5.2.19-1

Event History

Oct 8, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·06:33 PM
Dec 18, 2024
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-45231?

CVE-2024-45231 has been classified as a medium severity vulnerability due to its potential for user enumeration.

2

How do I fix CVE-2024-45231?

To fix CVE-2024-45231, upgrade your Django installation to versions 5.1.1, 5.0.9, or 4.2.16.

3

What versions of Django are affected by CVE-2024-45231?

CVE-2024-45231 affects Django versions prior to 5.1.1, including 5.0.9 and 4.2.16.

4

Can CVE-2024-45231 lead to account compromise?

CVE-2024-45231 allows attackers to enumerate valid email addresses but does not directly lead to account compromise.

5

Is user action required to exploit CVE-2024-45231?

Yes, an attacker must initiate a password reset request, making user action necessary for exploitation of CVE-2024-45231.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203