Password hash disclosure to "view only" admin users with custom user models
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.1.3, 6.0.10
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.1.3, 6.0.10.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Fix
- Fixed in 6.1.3, 6.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Django, the Python web framework, is affected, specifically versions 6.1 before 6.1.3 and 6.0 before 6.0.10, along with possibly older unsupported releases. The flaw can let staff users who only have view permission on a custom user model see full password hashes in the admin's read-only change form.
Read the original description
An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10. The `django.contrib.admin.utils.display_for_field()` function did not obfuscate the password field of user models other than `AUTH_USER_MODEL`, or of an `AUTH_USER_MODEL` inheriting its password field from a concrete parent model through multi-table inheritance, which allows authenticated staff users with only the view permission on such a model to obtain full password hashes via the read-only change form. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Aaron chen for reporting this issue.
Impact
- Widely used
django has 11.9m weekly downloads.Source: pypistats.org
12.1k packages depend on django.Source: deps.dev
What to do
Upgrade to a fixed version: 6.1.3, 6.0.10.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- djangoPyPI
From 6.1 · fixed in 6.1.3; From 6.0 · fixed in 6.0.10
Evidence 6
- Advisory
- Advisory
- Patch
- Patch
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.