CamelApplication · Apache
CVE-2017-5643
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's Validation Component is vulnerable against SSRF via remote DTDs and XXE.
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's Validation Component has an XML External Entity (XXE) and Server-Side Request Forgery (SSRF) vulnerability. The component processes XML without disabling external entity resolution, allowing attackers to inject malicious DTDs that force the server to make arbitrary HTTP requests to internal infrastructure or exfiltrate sensitive file contents.
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.16.0= 2.17.0= 2.17.1= 2.17.2= 2.17.3= 2.17.4= 2.17.5= 2.18.0= 2.18.1= 2.18.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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.
-
Identify Apache Camel versionLocate the camel-core JAR file in your deployment and check its version, or run: mvn dependency:tree | grep camel-core, or check your build artifact versionAffected if The version is 2.16.0 or lower, or one of 2.17.0 through 2.17.5, or one of 2.18.0 through 2.18.2
-
Confirm Validation component usageSearch your route definitions (Java DSL or XML DSL files) for usages of 'validate()' or the 'validation:' component namespace, for example: from("direct:start").validate(phase).to("mock:result")Affected if Your Camel routes explicitly use the Validation component to process XML documents
-
Check XML parser configuration for the Validation componentInspect the XML parser setup used with your Validation component. Look for SAXParserFactory, DocumentBuilderFactory, or XMLReader instances. Check if features like 'http://xml.org/sax/features/external-general-entities' and 'http://apache.org/xml/features/disallow-doctype-decl' are explicitly configuredAffected if The XML parser is configured with external entity resolution enabled (DTDs allowed) or no explicit security hardening has been applied to disable XXE
-
Verify DTD processing is enabledExamine your Camel validation route configuration or custom XML parser bean definitions. Check for properties such as setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false) or similar DTD-related settingsAffected if DTD processing is not explicitly disabled in your XML parser configuration, leaving the XXE and SSRF attack vector open
You are affected if you run any affected Apache Camel version AND use the Validation component without explicitly disabling external entity and DTD processing in your XML parser configuration.
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 dataDisable external entity processing and DTD processing in the XML parser configuration used by Camel's Validation component, or upgrade to a patched Apache Camel version that addresses this vulnerability.
Fix this in Camel
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5643 — 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-2017-5643 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