31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
===========================
|
|
Django 3.2.13 release notes
|
|
===========================
|
|
|
|
*April 11, 2022*
|
|
|
|
Django 3.2.13 fixes two security issues with severity "high" in
|
|
3.2.12 and a regression in 3.2.4.
|
|
|
|
CVE-2022-28346: Potential SQL injection in ``QuerySet.annotate()``, ``aggregate()``, and ``extra()``
|
|
====================================================================================================
|
|
|
|
:meth:`.QuerySet.annotate`, :meth:`~.QuerySet.aggregate`, and
|
|
:meth:`~.QuerySet.extra` methods were subject to SQL injection in column
|
|
aliases, using a suitably crafted dictionary, with dictionary expansion, as the
|
|
``**kwargs`` passed to these methods.
|
|
|
|
CVE-2022-28347: Potential SQL injection via ``QuerySet.explain(**options)`` on PostgreSQL
|
|
=========================================================================================
|
|
|
|
:meth:`.QuerySet.explain` method was subject to SQL injection in option names,
|
|
using a suitably crafted dictionary, with dictionary expansion, as the
|
|
``**options`` argument.
|
|
|
|
Bugfixes
|
|
========
|
|
|
|
* Fixed a regression in Django 3.2.4 that caused the auto-reloader to no longer
|
|
detect changes when the ``DIRS`` option of the ``TEMPLATES`` setting
|
|
contained an empty string (:ticket:`33628`).
|