SSRF in Djangoproject Django

CVE-2021-33571

In 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+..) .

Vulnerability class: SSRF (Server-Side Request Forgery)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

EPSS exploit prediction

EPSS: 0.053 (92.3th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 92nd percentile — 92.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2021-33571: held from 0.052 to 0.053.

EPSS over last 30 days · oldest: 0.052 · newest: 0.053 · change: +0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2021-33571?
CVE-2021-33571 is a high-severity vulnerability in Djangoproject Django, classified under Server-Side Request Forgery (SSRF). CVSS score: 7.5/10. Published 2021-06-08.
How severe is CVE-2021-33571?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2021-33571 known to be exploited?
4 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.