GHSA-6cw3-g6wv-c2xv BIT-django-2022-23833 CVE-2022-23833 PYSEC-2022-20

Infinite Loop in Django

High PyPI

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 49.53%; Chance of exploitation in the next 30 days. Higher than 98.89% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
Fix: 2.2.27; Upgrade django to this version or later

Description

An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2. Passing certain inputs to multipart forms could result in an infinite loop when parsing files.

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 2.2, < 2.2.27`	`2.2.27`
django	`>= 3.2, < 3.2.12`	`3.2.12`
django	`>= 4.0, < 4.0.2`	`4.0.2`
django	`>= 2.2, < 2.2.27` `>= 3.2, < 3.2.12` `>= 4.0, < 4.0.2`	`2.2.27` `3.2.12` `4.0.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 → `2.2.27`

pip

pip install --upgrade "django>=2.2.27"

poetry

poetry add "django>=2.2.27"

uv

uv add "django>=2.2.27"

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-835: Loop with Unreachable Exit Condition ('Infinite Loop')

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

References

Advisories

Write-ups

djangoproject.com/weblog/2022/feb/01/security-releases

Packages

github.com/django/django

Timeline

Feb 3, 2022 Published
Sep 20, 2024 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