dbcve.org
CamelApplication · Apache

CVE-2017-3159

CRITICAL · 9.8 CVSS v3.0 Published 2017-03-07
Fix available
A fix is available. Upgrade to after 2.18.1 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
Apache Camel's camel-snakeyaml component is vulnerable to Java object de-serialization 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-snakeyaml component in Apache Camel is vulnerable to unsafe Java object deserialization through the SnakeYAML library. When parsing untrusted YAML input, the component can deserialize malicious payloads leading to potential remote code execution.

MitigationUpgrade the snakeyaml library to a version that includes safe deserialization controls (e.g., SafeConstructor) or update Apache Camel to a version that bundles a patched snakeyaml dependency; also implement input validation and consider using the SafeConstructor pattern for YAML parsing.

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.14.4>= 2.17.0, <= 2.17.4>= 2.18.0, <= 2.18.1

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. Identify Apache Camel version
    Check the Apache Camel version deployed in your environment (e.g., via pom.xml dependency, JAR manifest, or running 'camel:info' endpoint if available)
    Affected if The installed version is 2.14.4 or earlier; OR 2.17.0 through 2.17.4; OR 2.18.0 through 2.18.1
  2. Locate camel-snakeyaml component
    Search for the camel-snakeyaml JAR in your classpath or dependencies, or check for routes using the 'snakeyaml' data format in your Camel route definitions
    Affected if The camel-snakeyaml component is present in your deployment
  3. Identify SnakeYAML library version
    Inspect the SnakeYAML library bundled with or referenced by your camel-snakeyaml component (check the transitive dependency version in your Maven pom or the JAR file name)
    Affected if The SnakeYAML version is older than the patched version that includes SafeConstructor controls (compare to vendor release notes for SafeConstructor availability)
  4. Determine if YAML input is untrusted
    Review your Camel routes and identify if the snakeyaml data format processes YAML from external or untrusted sources such as HTTP requests, message queues, file uploads, or network endpoints
    Affected if The camel-snakeyaml component processes YAML input originating from untrusted or external sources without additional validation

You are affected if your environment runs a vulnerable Apache Camel version with the camel-snakeyaml component processing untrusted YAML input, and the bundled SnakeYAML library lacks SafeConstructor-based deserialization controls.

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 a release after 2.18.1
Interim mitigation

Upgrade the snakeyaml library to a version that includes safe deserialization controls (e.g., SafeConstructor) or update Apache Camel to a version that bundles a patched snakeyaml dependency; also implement input validation and consider using the SafeConstructor pattern for YAML parsing.

Recommended fix High confidence

Apache Camel 2.19.0 or later (specifically upgrade camel-snakeyaml component to 2.19.0+)

  1. 1. Identify all projects using the camel-snakeyaml component with affected versions (2.14.x <= 2.14.4, 2.17.0-2.17.4, or 2.18.0-2.18.1).
  2. 2. Update the Maven dependency or OSGi bundle version for org.apache.camel:camel-snakeyaml to version 2.19.0 or later.
  3. 3. Rebuild and test the application to ensure the upgrade does not break existing functionality.
  4. 4. Redeploy the updated application to all affected environments.
Caveat Minimal - this is a security patch upgrade; however, test thoroughly as minor API changes may exist between 2.18.x and 2.19.0

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3159 — 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-3159 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