diff options
| author | Simon Charette <charette.s@gmail.com> | 2019-12-16 21:51:57 -0500 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-12-18 09:11:39 +0100 |
| commit | 5b1fbcef7a8bec991ebe7b2a18b5d5a95d72cb70 (patch) | |
| tree | 77991a30e32bb8f18971a89f23461b66714931fe /docs/releases/2.2.9.txt | |
| parent | f4647179ccd13c852563205273163b641d4b01a5 (diff) | |
Fixed CVE-2019-19844 -- Used verified user email for password reset requests.
Co-Authored-By: Florian Apolloner <florian@apolloner.eu>
Diffstat (limited to 'docs/releases/2.2.9.txt')
| -rw-r--r-- | docs/releases/2.2.9.txt | 20 |
1 files changed, 18 insertions, 2 deletions
diff --git a/docs/releases/2.2.9.txt b/docs/releases/2.2.9.txt index efd0cb4e1c..25a9374194 100644 --- a/docs/releases/2.2.9.txt +++ b/docs/releases/2.2.9.txt @@ -2,9 +2,25 @@ Django 2.2.9 release notes ========================== -*Expected January 2, 2020* +*December 18, 2019* -Django 2.2.9 fixes a data loss bug in 2.2.8. +Django 2.2.9 fixes a security issue and a data loss bug in 2.2.8. + +CVE-2019-19844: Potential account hijack via password reset form +================================================================ + +By submitting a suitably crafted email address making use of Unicode +characters, that compared equal to an existing user email when lower-cased for +comparison, an attacker could be sent a password reset token for the matched +account. + +In order to avoid this vulnerability, password reset requests now compare the +submitted email using the stricter, recommended algorithm for case-insensitive +comparison of two identifiers from `Unicode Technical Report 36, section +2.11.2(B)(2)`__. Upon a match, the email containing the reset token will be +sent to the email address on record rather than the submitted address. + +.. __: https://www.unicode.org/reports/tr36/#Recommendations_General Bugfixes ======== |