An XML External Entity (XXE) vulnerability in Multiple WSO2 Products
- 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 2.0.0, 4.0.0.311, 4.1.0.152, 4.2.0.122, 1.2.0.162, and 4 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: total
Summary
Due to the improper configuration of XML parser, user-supplied XML is parsed without applying sufficient restrictions, enabling XML External Entity (XXE) resolution in multiple WSO2 Products. A successful XXE attack could allow a remote, unauthenticated attacker to: • Read sensitive files from the server’s filesystem. • Perform denial-of-service (DoS) attacks, which can render the affected service unavailable.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
fixed in 2.0.0; From 4.0.0 · fixed in 4.0.0.311; From 4.1.0 · fixed in 4.1.0.152; From 4.2.0 · fixed in 4.2.0.122
- WSO2 WSO2 Enterprise Integrator
6.0.0, 6.1.0, 6.1.1, 6.2.0, 6.3.0, 6.4.0, 6.5.0, 6.6.0
- WSO2 WSO2 Enterprise Service Bus
4.9.0, 5.0.0
- WSO2 WSO2 Micro integrator
From 1.2.0 · fixed in 1.2.0.162; From 4.0.0 · fixed in 4.0.0.132; From 4.1.0 · fixed in 4.1.0.115; From 4.2.0 · fixed in 4.2.0.112
- WSO2 WSO2 Open Banking AM
1.5.0
- org.wso2.am:am-distribution-parentMaven
fixed in 2.1.0