Django Potential account hijack via password reset form
Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-19844US | critical9.8 | Exploit | ||
Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after cas… | ||||
02
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/155872/Django-Account-Hijack.htmlWEB
- https://docs.djangoproject.com/en/dev/releases/securityWEB
- https://github.com/advisories/GHSA-vfq6-hq5r-27r6ADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/302a4ff1e8b1c798aab97673909c7a3dfda42c26WEB
- https://github.com/django/django/commit/4d334bea06cac63dc1272abcec545b85136cca0eWEB
- https://github.com/django/django/commit/5b1fbcef7a8bec991ebe7b2a18b5d5a95d72cb70WEB
- https://github.com/django/django/commit/f4cff43bf921fcea6a29b726eb66767f67753fa2WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan