Skip to content
Fencer Intel
critical 9.8

CVE-2010-2076 json

Improper Input Validation in Apache CXF

published 2010-08-19 16 y ago modified 2026-06-16 4 mo ago also GHSA-v8q2-94f6-6xq2 , EUVD-2022-5318

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.8%
EPSS 9.8% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-2076 updated cvss 7.5

CXF: Insufficient constraints on Document Type Declarations (DTDs)

  • Red Hat JBoss SOA Platform 5 cxf
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.79% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • svn.apache.org http://svn.apache.org/repos/asf/cxf/trunk/security/CVE-2010-2076.pdf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven org.apache.cxf:cxf-rt-frontend-jaxrs
>=2.0.0, <2.0.13
>=2.1.0, <2.1.10
>=2.2.0, <2.2.9
2.0.13
2.1.10
2.2.9

Classification

Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.