GHSA-v6rh-hp5x-86rv BIT-django-2021-44420 CVE-2021-44420 PYSEC-2021-439

Potential bypass of an upstream access control based on URL paths in Django

High PyPI

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 2.42%; Chance of exploitation in the next 30 days. Higher than 84.18% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-287 Improper Authentication
Fix: 2.2.25; Upgrade django to this version or later

Description

In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths. This issue has low severity, according to the Django security policy.

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 2.2a1, < 2.2.25`	`2.2.25`
django	`>= 3.0a1, < 3.1.14`	`3.1.14`
django	`>= 3.2a1, < 3.2.10`	`3.2.10`
django	`>= 2.2, < 2.2.25` `>= 3.1, < 3.1.14` `>= 3.2, < 3.2.10`	`2.2.25` `3.1.14` `3.2.10`

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.25`

pip

pip install --upgrade "django>=2.2.25"

poetry

poetry add "django>=2.2.25"

uv

uv add "django>=2.2.25"

Severity breakdown

CVSS 4.0 0.0

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

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

CVSS 3.1 7.3

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

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

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it

Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

References

Advisories

Write-ups

djangoproject.com/weblog/2021/dec/07/security-releases

Packages

github.com/django/django

Timeline

Dec 8, 2021 Published
Nov 19, 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