dbcve.org
CamelApplication · Apache

CVE-2017-12634

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-15
Fix available
A fix is available. Upgrade to 2.19.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws.

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 · moderate confidence

The camel-castor component in Apache Camel versions 2.x before 2.19.4 and 2.20.x before 2.20.1 contains a Java deserialization vulnerability. The component deserializes untrusted data without proper validation, potentially allowing remote code execution through malicious serialized Java objects.

MitigationUpgrade Apache Camel to version 2.19.4 or later, or 2.20.1 or later. If immediate patching is not possible, disable or restrict the camel-castor component and implement network-level controls to limit exposure to untrusted inputs.

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
Affected:>= 2.0.0, < 2.19.4= 2.20.0

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed Apache Camel version
    Inspect the Camel library JAR files (e.g., camel-core-*.jar) in your application's classpath or dependency management, or run: java -jar yourapp.jar --version, or check your Maven/Gradle dependency tree for org.apache.camel:camel-core
    Affected if The version is 2.0.0 through 2.19.3, or exactly 2.20.0
  2. Identify if the camel-castor component is present
    Search for the camel-castor JAR file (camel-castor-*.jar) in your application's lib or dependencies, or check your Maven/Gradle dependencies for org.apache.camel:camel-castor
    Affected if The camel-castor component is included in your deployment
  3. Locate routes or configuration files using the castor component
    Search project source code and configuration files (XML, YAML, or Java DSL) for 'castor:' in route definitions, or for <route> elements containing a castor endpoint URI
    Affected if Routes or endpoints explicitly reference the castor component for data transformation
  4. Verify if deserialized data originates from untrusted sources
    Review your integration endpoints and data flows to determine whether the camel-castor component processes data from external or untrusted inputs such as HTTP requests, message queues, or file uploads
    Affected if The castor component processes deserialized data from external or untrusted sources without prior validation

You are affected if you run Apache Camel version 2.0.0-2.19.3 or 2.20.0, have the camel-castor component present, use it in routes, and it processes data from untrusted external sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.19.4 or later
Fixed in 2.19.4
Interim mitigation

Upgrade Apache Camel to version 2.19.4 or later, or 2.20.1 or later. If immediate patching is not possible, disable or restrict the camel-castor component and implement network-level controls to limit exposure to untrusted inputs.

Recommended fix High confidence

2.19.4 or later, or 2.20.1 or later (depending on your release line)

  1. 1. Identify the current Apache Camel version in use by checking your project dependencies (pom.xml, build.gradle, or similar).
  2. 2. Determine which release line (2.19.x or 2.20.x) you are currently using.
  3. 3. If using the 2.19.x line: upgrade Apache Camel to version 2.19.4 or later (preferably the latest 2.19.x release).
  4. 4. If using the 2.20.x line: upgrade Apache Camel to version 2.20.1 or later (preferably the latest 2.20.x release).
  5. 5. Update the camel-castor dependency version in your build configuration to match the upgraded Camel version.
  6. 6. Rebuild and test the application to ensure the upgrade does not break existing functionality.
  7. 7. Verify the fix by confirming the camel-castor component is no longer vulnerable to deserialization attacks.
Caveat Review Camel migration notes between minor versions for potential breaking changes; minor version upgrades may include API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12634 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12634 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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