Skip to content
Fencer Intel
medium 4.3

CVE-2014-0110 json

Uncontrolled Resource Consumption in Apache CXF

published 12y ago modified 4mo ago also GHSA-5xf9-3v63-ww6f , EUVD-2022-2677

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

Summary

Apache CXF before 2.6.14 and 2.7.x before 2.7.11 allows remote attackers to cause a denial of service (/tmp disk consumption) via a large invalid SOAP message.

Patch / fix

  • maven org.apache.cxf:cxf-core 2.6.14, 2.7.11
  • wss4j jboss enterprise application platform 6 1.6.15-1.redhat_1.1.ep6.el5
  • jbossts jboss enterprise application platform 6 1:4.17.15-5.Final_redhat_5.1.ep6.el5
  • jbossweb jboss enterprise application platform 6 7.3.2-1.Final_redhat_1.1.ep6.el5
  • resteasy jboss enterprise application platform 6 2.3.7.2-1.Final_redhat_1.1.ep6.el5
  • picketbox jboss enterprise application platform 6 4.0.19-8.SP8_redhat_1.1.ep6.el5
  • weld-core jboss enterprise application platform 6 1.1.17-4.SP3_redhat_1.1.ep6.el5
  • apache-cxf jboss enterprise application platform 6 2.7.11-3.redhat_3.1.ep6.el5
  • jboss-aesh jboss enterprise application platform 6 0.33.12-1.redhat_1.1.ep6.el5

red hat advisories RHSA-2014:0798RHSA-2014:0799

Is CVE-2014-0110 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2014-0110 updated cvss 3.5

CXF: Large invalid content could cause temporary space to fill

  • Red Hat OpenShift Enterprise 1 cxf
    affected: no fix planned “Will not fix”
  • Red Hat BPM Suite 6 cxf
    affected: no fix available
  • Red Hat JBoss BRMS 5 cxf
    affected: no fix planned “Will not fix”
  • Red Hat JBoss BRMS 6 cxf Red Hat JBoss Fuse Service Works 6 cxf Red Hat JBoss Portal 6 cxf
    affected: no fix available
  • Red Hat OpenShift Enterprise 2 cxf
    affected: no fix planned “Will not fix”
  • Red Hat JBoss A-MQ 6.1
    fixed: vendor fix RHSA-2014:1351
  • Red Hat JBoss BPMS 6.0
    fixed: vendor fix RHSA-2015:0851
  • Red Hat JBoss BRMS 6.0
    fixed: vendor fix RHSA-2015:0850
show 5 more
  • Red Hat JBoss Enterprise Application Platform 6.2
    fixed: vendor fix RHSA-2014:0797
  • Red Hat JBoss Enterprise Application Platform 6.2 for RHEL 5 Server wss4j 1.6.15-1.redhat_1.1.ep6.el5, apache-cxf 2.7.11-3.redhat_3.1.ep6.el5, jboss-aesh 0.33.12-1.redhat_1.1.ep6.el5, jbossweb 7.3.2-1.Final_redhat_1.1.ep6.el5, picketbox 4.0.19-8.SP8_redhat_1.1.ep6.el5, weld-core 1.1.17-4.SP3_redhat_1.1.ep6.el5, +71 more
    fixed: vendor fix RHSA-2014:0798
  • Red Hat JBoss Enterprise Application Platform 6.2 for RHEL 6 Server wss4j 1.6.15-1.redhat_1.1.ep6.el6, apache-cxf 2.7.11-3.redhat_3.1.ep6.el6, jboss-aesh 0.33.12-1.redhat_1.1.ep6.el6, jbossweb 7.3.2-1.Final_redhat_1.1.ep6.el6, picketbox 4.0.19-8.SP8_redhat_1.1.ep6.el6, weld-core 1.1.17-4.SP3_redhat_1.1.ep6.el6, +71 more
    fixed: vendor fix RHSA-2014:0799
  • Red Hat JBoss Fuse 6.1
    fixed: vendor fix RHSA-2014:1351
  • Red Hat JBoss Portal 6.2
    fixed: vendor fix RHSA-2015:1009

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

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

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected packages

ecosystem package affected fixed in
maven org.apache.cxf:cxf-core
<2.6.14
>=2.7.0, <2.7.11
2.6.14
2.7.11

Classification

Weakness
  • CWE-399 Resource Management Errors
  • CWE-400 Uncontrolled Resource Consumption

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.