GHSA-qrw5-5h28-6cmg BIT-django-2022-41323 CVE-2022-41323 PYSEC-2022-304

Django denial-of-service vulnerability in internationalized URLs

High PyPI

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 3.75%; Chance of exploitation in the next 30 days. Higher than 89.88% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-1333 Inefficient Regular Expression Complexity
Fix: 3.2.16; Upgrade django to this version or later

Description

In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular expression.

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 3.2, < 3.2.16`	`3.2.16`
django	`>= 4.0, < 4.0.8`	`4.0.8`
django	`>= 4.1, < 4.1.2`	`4.1.2`
django	`>= 3.2, < 3.2.16` `>= 4.0, < 4.0.8` `>= 4.1, < 4.1.2`	`3.2.16` `4.0.8` `4.1.2`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

django PyPI → `3.2.16`

pip

pip install --upgrade "django>=3.2.16"

poetry

poetry add "django>=3.2.16"

uv

uv add "django>=3.2.16"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: None
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): None
Integrity (vulnerable system): None
Availability (vulnerable system): High
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Weakness

CWE-1333: Inefficient Regular Expression Complexity

The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.

How to prevent it

Architecture and Design: Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
System Configuration: Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
Implementation: Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
Implementation: Limit the length of the input that the regular expression will process.

References

Advisories

Write-ups

djangoproject.com/weblog/2022/oct/04/security-releases

Packages

github.com/django/django

Timeline

Oct 16, 2022 Published
Jun 10, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-q238-5cxm-5c9h Django GeoDjango vulnerable to denial of service through deeply nested geometry collections	Medium	Also affects django
GHSA-wvqv-fj8w-qmhm Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing	High	Also affects django
GHSA-8qcx-xf44-272x Django: DomainNameValidator permits newline characters that may enable HTTP header injection	Medium	Also affects django
GHSA-crhf-3pfg-w68w Django: GDALRaster may over-read heap memory when constructed from bytes	Medium	Also affects django
GHSA-3h9f-r86x-qvjx Django: cache middleware may expose private responses when unrelated request cookies are present	Medium	Also affects django
GHSA-8cjm-8mp7-r2xf Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling	Medium	Also affects django
GHSA-mm6v-q8q9-pgcf Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake	Low	Also affects django
GHSA-h7pc-vwp9-298g Django: signed cookies are vulnerable to salt namespace collisions	Medium	Also affects django

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor