CVE-2016-5003 Apache XML-RPC vulnerable to Deserialization of Untrusted Data
Critical 9.8
Published
Updated
Check this codebase for CVE-2016-5003 and fix it if it is affected.
What it is: CVE-2016-5003 is a critical unsafe deserialization vulnerability in n/a, published on 27 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5003 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.apache.xmlrpc:xmlrpc (Maven): affected all versions up to 3.1.3; no fix listed
- org.apache.xmlrpc:xmlrpc (Maven): affected all versions up to 3.1.3; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2016-5003/ (Markdown: https://insights.sbomify.com/CVE-2016-5003/index.md)
Remote attackers can execute arbitrary code by sending a crafted serialized Java object to the Apache XML-RPC library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-5003?
CVE-2016-5003 is a critical unsafe deserialization vulnerability in n/a, published on 27 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Apache XML-RPC (aka ws-xmlrpc) library 3.1.3, as used in Apache Archiva, allows remote attackers to execute arbitrary code via a crafted serialized Java object in an <ex:serializable> element.
Weakness: CWE-502
Which versions are affected by CVE-2016-5003?
2 open source packages ship an affected version, including org.apache.xmlrpc:xmlrpc. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.xmlrpc:xmlrpc Maven | All versions to 3.1.3 | None |
org.apache.xmlrpc:xmlrpc Maven | All versions to 3.1.3 | None |
Linux distribution packages (38)
xmlrpc3 Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-client Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-client-devel Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-common Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-common-devel Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-javadoc Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-server Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-server-devel Red Hat:enterprise_linux:6::server | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3 Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-client Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-client-devel Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-common Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-common-devel Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-javadoc Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-server Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc3-server-devel Red Hat:enterprise_linux:6::workstation | All versions | 0:3.0-4.17.el6_9 |
xmlrpc Red Hat:enterprise_linux:7::client | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-client Red Hat:enterprise_linux:7::client | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-common Red Hat:enterprise_linux:7::client | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-javadoc Red Hat:enterprise_linux:7::client | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-server Red Hat:enterprise_linux:7::client | All versions | 1:3.1.3-9.el7_5 |
xmlrpc Red Hat:enterprise_linux:7::computenode | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-client Red Hat:enterprise_linux:7::computenode | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-common Red Hat:enterprise_linux:7::computenode | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-javadoc Red Hat:enterprise_linux:7::computenode | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-server Red Hat:enterprise_linux:7::computenode | All versions | 1:3.1.3-9.el7_5 |
xmlrpc Red Hat:enterprise_linux:7::hypervisor | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-client Red Hat:enterprise_linux:7::hypervisor | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-common Red Hat:enterprise_linux:7::hypervisor | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-javadoc Red Hat:enterprise_linux:7::hypervisor | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-server Red Hat:enterprise_linux:7::hypervisor | All versions | 1:3.1.3-9.el7_5 |
xmlrpc Red Hat:enterprise_linux:7::server | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-client Red Hat:enterprise_linux:7::server | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-common Red Hat:enterprise_linux:7::server | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-javadoc Red Hat:enterprise_linux:7::server | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-server Red Hat:enterprise_linux:7::server | All versions | 1:3.1.3-9.el7_5 |
xmlrpc Red Hat:enterprise_linux:7::workstation | All versions | 1:3.1.3-9.el7_5 |
xmlrpc-client Red Hat:enterprise_linux:7::workstation | All versions | 1:3.1.3-9.el7_5 |
Products include Apache Ws-Xmlrpc.
How do I fix CVE-2016-5003?
Upgrade to a fixed version.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2016-5003 being exploited?
There is no known exploitation of CVE-2016-5003 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-4gqp-296r-j5mq, RHSA-2018:1779, RHSA-2018:1780, RHSA-2018:1784, RHSA-2018:2317.