Skip to content
Fencer Intel
high 7.5

CVE-2019-0188 json

XML External Entity injection in Apache Camel

published 7y ago modified 4mo ago also GHSA-h896-mx9x-g32g , EUVD-2019-0466

cvss
7.5
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 Camel prior to 2.24.0 contains an XML external entity injection (XXE) vulnerability (CWE-611) due to using an outdated vulnerable JSON-lib library. This affects only the camel-xmljson component, which was removed.

Patch / fix

  • maven org.apache.camel:camel-core 2.24.0
  • apache camel 2.24.0

Is CVE-2019-0188 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-2019-0188 updated cvss 5.8

camel-xmljson: XML external entity injection vulnerability inoutdated JSON-lib library

  • Red Hat Fuse 7 camel-xmljson camel-xmljson
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse 6 camel-xmljson camel-xmljson Red Hat JBoss Fuse Service Works 6 camel-xmljson camel-xmljson
    affected: no fix planned “Out of support scope”

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.78% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-core
<2.24.0
2.24.0
maven org.apache.camel:camel-xmljson
<=2.23.4
no fix listed

Affected products

  • Apache Apache Camel

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

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.