LiveActive security incident?Get immediate response
CVE Record

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,...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Django versions accepted unusual IPv4 forms with leading zeroes. If an application used Django validators to decide whether an address was allowed or blocked, that ambiguity could let a request bypass IP-based access rules. The risk is highest where IP validation directly gates admin, internal, or restricted functionality.

Executive priority

Prioritize remediation for internet-facing or partner-facing Django applications where IP checks protect sensitive routes. For other deployments, handle through normal dependency patching, because no active exploitation is cited in the provided sources.

Technical view

CVE-2021-33571 affects 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 failed to prohibit leading zero characters in octal literals. validate_ipv4_address and validate_ipv46_address are noted as unaffected with Python 3.9.5+.

Likely exposure

Exposure is likely limited to Django applications or downstream products using affected Django versions and relying on these validators for IP-based access control, allowlists, blocklists, or URL trust decisions. Applications not using these validators for security decisions are less exposed.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Public Django materials describe a validation flaw that may enable access-control bypass when IP address checks depend on the affected validators.

Researcher notes

The key research question is whether validator output feeds an authorization decision. Python 3.9.5+ narrows exposure for validate_ipv4_address and validate_ipv46_address, but URLValidator remains listed in the CVE description. Evidence supplied does not include CVSS, CWE, or exploit-in-the-wild confirmation.

Mitigation direction

  • Upgrade Django to 2.2.24, 3.1.12, 3.2.4, or later supported releases.
  • Review vendor or distribution advisories for packaged Django or embedded product dependencies.
  • Audit IP-based access controls that depend on Django URL or IP validators.
  • Avoid relying only on string-format validation for security authorization decisions.

Validation and detection

  • Inventory deployed Django versions across applications and container images.
  • Search code for URLValidator, validate_ipv4_address, and validate_ipv46_address in security paths.
  • Confirm whether affected validators gate allowlists, blocklists, admin access, or internal routes.
  • Add regression tests confirming leading-zero IPv4 notation is rejected in security checks.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-33571 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.