Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 3 Jun 2020 11:46:19 +0200
From: Carlton Gibson <>
Subject: Django security releases issued: 3.0.7, and 2.2.13 for CVE-2020-13254
 & CVE-2020-13596. <>

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

CVE-2020-13254: Potential data leakage via malformed memcached keys

In cases where a memcached backend does not perform key validation, passing
malformed cache keys could result in a key collision, and potential data
leakage. In order to avoid this vulnerability, key validation is added to the
memcached cache backends.

Thank you to Dan Palmer for the report and patch.

CVE-2020-13596: Possible XSS via admin ``ForeignKeyRawIdWidget``

Query parameters for the admin ``ForeignKeyRawIdWidget`` were not properly URL
encoded, posing an XSS attack vector. ``ForeignKeyRawIdWidget`` now
ensures query parameters are correctly URL encoded.

Thank you to Jon Dufresne for the report and patch.

Affected supported versions

* Django master branch
* Django 3.1 (currently at alpha status)
* Django 3.0
* Django 2.2


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


* On the `master branch <>`__
* On the `3.1 release branch <>`__
* On the `3.0 release branch <>`__
* On the `2.2 release branch <>`__


* On the `master branch <>`__
* On the `3.1 release branch <>`__
* On the `3.0 release branch <>`__
* On the `2.2 release branch <>`__

The following releases have been issued:

* Django 3.0.7 (`download Django 3.0.7 <>`_ | `3.0.7 checksums <>`_)
* Django 2.2.13 (`download Django 2.2.13 <>`_ | `2.2.13 checksums <>`_)

The PGP key ID used for these releases is Carlton Gibson: E17DF5C82B4F9D00.

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

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.