CVE-2014-0002: High severity Apache Camel vulnerability

Published Jan 8, 2014
·
Updated

It was found that the Apache Camel XSLT component would resolve entities in XML messages when transforming them using an xslt: route. A remote attacker able to submit messages to an xslt: Camel route could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks.

Other sources

The XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary files and possibly have other unspecified impact via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Affected Software

33 affected componentsFixes available
maven/org.apache.camel:camel-core>=2.12.0<2.12.3
2.12.3
maven/org.apache.camel:camel-core<2.11.4
2.11.4
Apache Camel<=2.11.3
Apache Camel=1.0.0
Apache Camel=1.1.0
Apache Camel=1.2.0
Apache Camel=1.3.0
Apache Camel=1.4.0
Apache Camel=1.5.0
Apache Camel=1.6.0
Apache Camel=1.6.1
Apache Camel=1.6.2
Apache Camel=1.6.3
Apache Camel=1.6.4
Apache Camel=2.0.0
Apache Camel=2.0.0-milestone1
Apache Camel=2.0.0-milestone2
Apache Camel=2.0.0-milestone3
Apache Camel=2.1.0
Apache Camel=2.10.0
Apache Camel=2.10.1
Apache Camel=2.10.2
Apache Camel=2.10.3
Apache Camel=2.10.4
Apache Camel=2.10.5
Apache Camel=2.10.6
Apache Camel=2.10.7
Apache Camel=2.11.0
Apache Camel=2.11.1
Apache Camel=2.11.2
Apache Camel=2.12.0
Apache Camel=2.12.1
Apache Camel=2.12.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 2.12.3
  2. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 2.11.4
  3. Upgrade

    Upgrade Apache Camel XSLT component to a version that resolves this vulnerability.

    Fixed in 2.11.4
  4. Upgrade

    Upgrade Apache Camel XSLT component to a version that resolves this vulnerability.

    Fixed in 2.12.3

Event History

Jan 8, 2014
Data Sourced
01:57 AM
DescriptionSeverityAffected Software
Mar 20, 2014
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Mar 21, 2014
Data Sourced
via NVD·04:38 AM
DescriptionSeverityWeaknessAffected Software
Oct 16, 2018
Advisory Published
11:13 PM

Frequently Asked Questions

1

What is the severity of CVE-2014-0002?

CVE-2014-0002 is classified as a critical vulnerability because it allows remote attackers to read arbitrary files on the server.

2

How do I fix CVE-2014-0002?

To address CVE-2014-0002, upgrade the Apache Camel software to version 2.11.4 or 2.12.3 or later.

3

Which versions of Apache Camel are affected by CVE-2014-0002?

CVE-2014-0002 affects Apache Camel versions up to and including 2.11.3 and versions 1.0.0 through 2.11.3.

4

What types of attacks can exploit CVE-2014-0002?

CVE-2014-0002 can be exploited by an attacker who can submit XML messages to an xslt: route, leading to potential file disclosure.

5

Are there any mitigations for CVE-2014-0002?

There are no specific mitigations; the best practice is to apply the fix by upgrading to the recommended versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203