Severity
- CVSS 3.x
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| All commits before 358973a12eb3105ba084a2d594428a19223b8582 | 358973a12eb3105ba084a2d594428a19223b8582 |
| 2a62cdcfec85938f40abb2e9e6a9ff497e02afe8 to before c494d90c195a739a7298b073eaa6ed987c2fd0bc | c494d90c195a739a7298b073eaa6ed987c2fd0bc |
| 2a04e24d2dfc8e60a66e4369d970913cb2112d91 through 2a04e24d2dfc8e60a66e4369d970913cb2112d91 | No fix listed |
Also listed as affected (51)
| |
Description
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.)
References
- Webpacketstormsecurity.com/files/155872/Django-Account-Hijack.html ↗
- Webgroups.google.com/forum/#%21topic/django-announce/3oaB2rVH3a0 ↗
- Weblists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HCM2DPUI7TOZWN4A6JFQFUVQ2XGE7GUD/ ↗
- Webseclists.org/bugtraq/2020/Jan/9 ↗
- Advisorydocs.djangoproject.com/en/dev/releases/security/ ↗
- Advisorysecurity.gentoo.org/glsa/202004-17 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20200110-0003/ ↗
- Advisoryusn.ubuntu.com/4224-1/ ↗
- Advisorywww.debian.org/security/2020/dsa-4598 ↗
- Advisorywww.djangoproject.com/weblog/2019/dec/18/security-releases/ ↗