Summary
Improper Input Validation in Apache CXF
Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry, Apache jUDDI, Apache Geronimo, and other products, does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service (CPU and memory consumption) via a crafted DTD, as demonstrated by an entity declaration in a request to samples/wsdl_first_pure_xml, a similar issue to CVE-2010-1632.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.cxf:cxf-rt-frontend-jaxrs to 2.0.13 or later; org.apache.cxf:cxf-rt-frontend-jaxrs to 2.1.10 or later; org.apache.cxf:cxf-rt-frontend-jaxrs to 2.2.9 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2010-2076? CVE-2010-2076 is a high-severity improper input validation vulnerability in org.apache.cxf:cxf-rt-frontend-jaxrs (maven), affecting versions >= 2.0.0, < 2.0.13. It is fixed in 2.0.13, 2.1.10, 2.2.9. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of org.apache.cxf:cxf-rt-frontend-jaxrs are affected by CVE-2010-2076? org.apache.cxf:cxf-rt-frontend-jaxrs (maven) versions >= 2.0.0, < 2.0.13 is affected.
- Is there a fix for CVE-2010-2076? Yes. CVE-2010-2076 is fixed in 2.0.13, 2.1.10, 2.2.9. Upgrade to this version or later.
- Is CVE-2010-2076 exploitable, and should I be worried? Whether CVE-2010-2076 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2010-2076 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2010-2076?
- Upgrade
org.apache.cxf:cxf-rt-frontend-jaxrsto 2.0.13 or later - Upgrade
org.apache.cxf:cxf-rt-frontend-jaxrsto 2.1.10 or later - Upgrade
org.apache.cxf:cxf-rt-frontend-jaxrsto 2.2.9 or later
- Upgrade