Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 18 Dec 2019 10:28:40 +0100
From: Mariusz Felisiak <>
Subject: Django: CVE-2019-19844: Potential account hijack via password reset

In accordance with `our security release policy 
<>`_, the 
Django team is issuing `Django 3.0.1 
<>`_, `Django 2.2.9 
<>`_ and `Django 
1.11.27 <>`_. 
These release addresses the security issue detailed below. We encourage 
all users of Django to upgrade as soon as possible.

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

In order to avoid this vulnerability, password reset requests now 
compare the
submitted email using the stricter, recommended algorithm for 
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.

.. __:

Affected supported versions

* Django master branch
* Django 3.0
* Django 2.2
* Django 2.1


Patches to resolve the issue have been applied to Django's master branch and
the 3.0, 2.2, and 1.11 release branches. The patches may be obtained 
from the following changesets:

* On the `master branch 
* On the `3.0 release branch 
* On the `2.2 release branch 
* On the `1.11 release branch 

The following releases have been issued:

* Django 3.0.1 (`download Django 3.0.1 
<>`_ | 
`3.0.1 checksums 
* Django 2.2.9 (`download Django 2.2.9 
<>`_ | 
`2.2.9 checksums 
* Django 1.11.27 (`download Django 1.11.27 
| `1.11.27 checksums 

The PGP key ID used for these releases is Mariusz Felisiak: 

General notes regarding security reporting

As always, we ask that potential security issues be reported via
private email to ````, and not via Django's
Trac instance or the django-developers list. Please see `our security
policies <>`_ for further

This issue was known publicly, therefore we fixed the issue as soon as 
possible without the usual `prenotification process 

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.