Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
3.2.4In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .
From the CVE record · mitre
Django's URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals in the affected versions. An attacker may bypass IP-based access controls if an application relies on these validators. The input does not specify whether authentication or user interaction is required; validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5 or later.
Teams running the PyPI django package should check versions 2.2 before 2.2.24, 3.0 before 3.1.12, and 3.2 before 3.2.4, including prereleases in those ranges.