The XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 is not configured to deny the…
Fix:upgrade odata-client-core and odata-server-core Versions ↓
Apache · Olingo
The XML entity deserializer in Apache Olingo versions 4.0.0 through 4.6.0 fails to block resolution of external entities. An attacker who can send a request with the "application/xml" content type that triggers entity deserialization can exploit this to carry out XXE attacks.
Official description · CVE.org
The XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 is not configured to deny the resolution of external entities. Request with content type "application/xml", which trigger the deserialization of entities, can be used to trigger XXE attacks.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 16 months after disclosure. Public exploit code (Exploit-DB) appeared 7 days after disclosure.
- Disclosedday 0
- Public exploit codeExploit-DB+7 days
- First seen exploitedVulnCheck KEV evidence+16 mo
Affected versions and fixes
as published in the CVE recordApache Olingo
Affected: 4.0.0 to 4.6.0
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSV2 packages in 1 ecosystem. No single main package: each of these ships the affected code.
- Mavenorg.apache.olingo:odata-client-coreAffected: 4.0.0 up to 4.7.0Upgrade to 4.7.0 or later
- Mavenorg.apache.olingo:odata-server-coreAffected: 4.0.0 up to 4.7.0Upgrade to 4.7.0 or later