Ce mail provient de l'extérieur, restons vigilants

=====================================================================

                            CERT-Renater

                Note d'Information No. 2025/VULN659
_____________________________________________________________________

DATE                : 02/10/2025

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Django versions prior to 5.2.7,
                                    5.1.13, 4.2.25.

=====================================================================
https://www.djangoproject.com/weblog/2025/oct/01/security-releases/
_____________________________________________________________________

Django security releases issued: 5.2.7, 5.1.13, and 4.2.25
Posted by Jacob Walls on 1 octobre 2025

In accordance with our security release policy, the Django team is
issuing releases for Django 5.2.7, Django 5.1.13, and Django 4.2.25.
These releases address the security issues detailed below. We
encourage all users of Django to upgrade as soon as possible.
CVE-2025-59681: Potential SQL injection in QuerySet.annotate(),
alias(), aggregate(), and extra() on MySQL and MariaDB

QuerySet.annotate(), QuerySet.alias(), QuerySet.aggregate(), and
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 on MySQL and
MariaDB.

Thanks to sw0rd1ight for the report.

This issue has severity "high" according to the Django security
policy.
CVE-2025-59682: Potential partial directory-traversal via
archive.extract()

The django.utils.archive.extract() function, used by
startapp --template and startproject --template, allowed partial
directory-traversal via an archive with file paths sharing a
common prefix with the target directory.

Thanks to stackered for the report.

This issue has severity "low" according to the Django security
policy.


Affected supported versions

    Django main
    Django 6.0 (currently at alpha status)
    Django 5.2
    Django 5.1
    Django 4.2


Resolution

Patches to resolve the issue have been applied to Django's main,
6.0 (currently at alpha status), 5.2, 5.1, and 4.2 branches. The
patches may be obtained from the following changesets.
CVE-2025-59681: Potential SQL injection in QuerySet.annotate(),
alias(), aggregate(), and extra() on MySQL and MariaDB

    On the main branch
    On the 6.0 branch
    On the 5.2 branch
    On the 5.1 branch
    On the 4.2 branch

CVE-2025-59682: Potential partial directory-traversal via
archive.extract()

    On the main branch
    On the 6.0 branch
    On the 5.2 branch
    On the 5.1 branch
    On the 4.2 branch

The following releases have been issued

    Django 5.2.7 (download Django 5.2.7 | 5.2.7 checksums)
    Django 5.1.13 (download Django 5.1.13 | 5.1.13 checksums)
    Django 4.2.25 (download Django 4.2.25 | 4.2.25 checksums)

The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7
General notes regarding security reporting

As always, we ask that potential security issues be reported
via private email to security@djangoproject.com, and not via
Django's Trac instance, nor via the Django Forum. Please see
our security policies for further information.


=========================================================
+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=========================================================