Potential denial-of-service vulnerability in XML serializer text extraction
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.9, 5.1.15, 4.2.27
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27. Algorithmic complexity in `django.core.serializers.xml_serializer.getInnerText()` allows a remote attacker to cause a potential denial-of-service attack triggering CPU and memory exhaustion via specially crafted XML input processed by the XML `Deserializer`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- django
From 5.2 · fixed in 5.2.9; From 5.1 · fixed in 5.1.15; From 4.2 · fixed in 4.2.27
- djangoPyPI
From 5.2a1 · fixed in 5.2.9
- djangoPyPI
From 5.1a1 · fixed in 5.1.15
- djangoPyPI
From 4.2a1 · fixed in 4.2.27
- djangoPyPI
From 4.2 · fixed in 4.2.27; From 5.1 · fixed in 5.1.15; From 5.2 · fixed in 5.2.9