CamelApplication · Apache
CVE-2019-0188
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Camel versions prior to 2.24.0 contain an XXE vulnerability (CWE-611) in the camel-xmljson component due to dependency on an outdated JSON-lib library with known XXE flaws. The vulnerable component has been entirely removed from the codebase.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CamelApplication
< 2.24.0= 11.1.1.9.0= 13.3.0.0= 13.4.0.0= 12.0.0= 12.1.0= 12.1.3.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Apache Camel versionLocate the camel-core JAR file in your deployment and inspect its MANIFEST.MF file, or run: mvn dependency:tree | grep camel-core, or check your dependency management file (pom.xml, build.gradle) for the camel versionAffected if The version is less than 2.24.0
-
Identify camel-xmljson presenceSearch your classpath or dependencies for camel-xmljson JAR file, or run: mvn dependency:tree | grep xmljson, or search for 'camel-xmljson' in your build configuration filesAffected if The camel-xmljson component is present in your runtime classpath or loaded as a Camel route component
-
Check Camel route definitions for xmljson usageInspect your Camel route XML files (*.xml), Java route classes, or Spring/Blueprint configuration files for references to 'xmljson' in <route> definitions or DataFormat definitionsAffected if Routes explicitly use xmljson DataFormat or component
-
Verify XML input processing configurationReview any Camel endpoints or routes that accept XML input and pass it through json/xml conversion, particularly where untrusted XML could be processedAffected if Your application processes XML input through Camel routes that may invoke the vulnerable xmljson DataFormat
You are affected if your Apache Camel version is below 2.24.0 AND the camel-xmljson component is present and actively used in your application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.24.0
Remove or migrate away from the camel-xmljson component entirely, as it is no longer maintained. Users must find alternative JSON-XML conversion approaches or pin to a safe version if continued use is absolutely necessary.
Fix this in Camel
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0188 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data