Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 3 Feb 2020 10:56:32 +0100
From: Carlton Gibson <>
Subject: Django 3.0.3, 2.2.10 and 1.11.28: CVE-2020-7471: Potential SQL
 injection via ``StringAgg(delimiter)`` <>

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

Affected supported versions

* Django master branch
* Django 3.0
* Django 2.2
* Django 1.11

CVE-2020-7471: Potential SQL injection via ``StringAgg(delimiter)``

``django.contrib.postgres.aggregates.StringAgg`` aggregation function was
subject to SQL injection, using a suitably crafted ``delimiter``.

Thank you to Simon Charette for the report and patch. 


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.3 (`download Django 3.0.3 <>`_ | `3.0.3 checksums <>`_)
* Django 2.2.10 (`download Django 2.2.10 <>`_ | `2.2.10 checksums <>`_)
* Django 1.11.28 (`download Django 1.11.28 <>`_ | `1.11.28 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.