CVE-2019-17570
CRITICALCVE-2019-17570 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.xmlrpc:xmlrpc. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2019-17570 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insecure Deserialization in Apache XML-RPC
Real-World Exposure
org.apache.xmlrpc:xmlrpcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code.
Apache XML-RPC is no longer maintained and this issue will not be fixed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.xmlrpc:xmlrpc | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
An untrusted deserialization was found in the org.apache.xmlrpc.parser.X…
An untrusted deserialization was found in the org.apache.xmlrpc.parser.X…
An untrusted deserialization was found in the org.apache.xmlrpc.parser.X…
An untrusted deserialization was found in the org.apache.xmlrpc.parser.X…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.xmlrpc:xmlrpc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of org.apache.xmlrpc:xmlrpc has shipped for CVE-2019-17570 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-17570 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-17570. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Enterprise Linux 7 provides vulnerable version of xmlrpc via the Optional repository. As the Optional repository is not supported, this issue is not planned to be addressed there. Red Hat Virtualization Manager uses xmlrpc only for internal communication with the scheduler. Since this is a component of the…
Frequently Asked Questions
Is CVE-2019-17570 in your dependencies?
O3 detects CVE-2019-17570 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.