CamelApplication · Apache
CVE-2015-0264
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 · uneditedMultiple XML external entity (XXE) vulnerabilities in builder/xml/XPathBuilder.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allow remote attackers to read arbitrary files via an external entity in an invalid XML (1) String or (2) GenericFile object in an XPath query.
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 confidenceXXE vulnerability in Apache Camel's XPathBuilder allows remote attackers to read arbitrary files by injecting malicious external entity references into XML input. The flaw exists when XPath queries are constructed from String or GenericFile objects containing invalid XML with external entity declarations.
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.13.3= 2.14.0= 2.14.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Identify Apache Camel installationLocate the camel-core JAR file or check your project's dependency management (Maven pom.xml, Gradle build.gradle) for the Apache Camel version. Search for files named camel-core-*.jar or examine dependency version declarations.Affected if The installed version is 2.13.3 or earlier, or exactly 2.14.0 or 2.14.1
-
Verify XPathBuilder usage with XML inputSearch your codebase for imports and usage of org.apache.camel.builder.xml.XPathBuilder. Review routes and processors that invoke XPathBuilder with data from external or untrusted sources such as HTTP requests, file uploads, or message payloads.Affected if XPathBuilder is used to evaluate XPath expressions against XML input derived from String or GenericFile objects
-
Inspect XML parser configurationReview your Camel XML parser setup. Check if the XMLInputFactory or DocumentBuilderFactory instances used with XPathBuilder have been configured to disable external entity resolution (look for properties such as XMLConstants.ACCESS_EXTERNAL_DTD, XMLConstants.ACCESS_EXTERNAL_SCHEMA, or the entity expansion limit settings).Affected if External entity resolution is enabled or the parser has not been explicitly hardened against XXE attacks
-
Check XML input validationExamine how XML data enters your Camel routes. Look for validation or sanitization of XML payloads before they reach XPathBuilder, including schema validation (XSD) or input filtering mechanisms.Affected if XML input is passed directly to XPathBuilder without prior validation or sanitization, or if validation schemas do not explicitly prohibit external entities
-
Review GenericFile and String-based XPath usageSearch for routes using endpoints such as file:, ftp:, or direct: that feed into XPathBuilder. Identify any code paths where XPath expressions are built dynamically from file content or string payloads that could contain crafted XML.Affected if XPath queries are constructed from GenericFile or String objects containing potentially untrusted XML content
You are affected if you run Apache Camel version 2.13.3 or earlier, or 2.14.0-2.14.1, and your application uses XPathBuilder to process XML input from untrusted sources without disabling external entity resolution in the XML parser.
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 dataUpgrade Apache Camel to version 2.13.4, 2.14.2, or later. Alternatively, disable external entity resolution in XML parsers used with XPathBuilder and validate/sanitize XML input before processing.
Fix this in Camel
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0264 — 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-2015-0264 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