Jaxp13 XPath XXE via StreamSource and SAXSource
- 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.0.1.1, 4.1.3.1, 4.0.19, 3.1.9, 5.0.2, and 1 more
- 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: yes
- Technical impact: partial
Summary
Jaxp13XPathTemplate evaluated XPath expressions for StreamSource and SAXSource inputs using a code path that parsed attacker-controlled XML with the JDK's default DocumentBuilderFactory behavior instead of Spring's hardened parser configuration. Applications that evaluate XPath against untrusted XML payloads could therefore be exposed to XML External Entity (XXE) style attacks. Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring Web Services
From 5.0.0 · fixed in 5.0.1.1; From 4.1.0 · fixed in 4.1.3.1; From 4.0.0 · fixed in 4.0.19; From 3.1.0 · fixed in 3.1.9
- org.springframework.ws:spring-xmlMaven
From 5.0.0 · fixed in 5.0.2
- org.springframework.ws:spring-xmlMaven
From 4.1.0 · fixed in 4.1.4
- org.springframework.ws:spring-xmlMaven
From 4.0.0 · through 4.0.18
- org.springframework.ws:spring-xmlMaven
From 3.1.0 · through 3.1.8