CamelApplication · Apache
CVE-2017-12633
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 · uneditedThe camel-hessian 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 confidenceThe camel-hessian component in Apache Camel versions before 2.19.4 and 2.20.1 is vulnerable to unsafe Java object deserialization. The Hessian protocol relies on Java serialization, and when deserializing untrusted data without proper validation or security controls, it allows attackers to potentially execute arbitrary code via malicious serialized objects.
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.0.0, < 2.19.4>= 2.20.0, < 2.20.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Camel versionLocate the camel-core JAR file or check the project's dependency management (Maven pom.xml, Gradle build file) to determine the exact Apache Camel version installed in your environment.Affected if The installed version is 2.0.0 through 2.19.3, or 2.20.0.
-
Locate camel-hessian componentSearch for the camel-hessian JAR file in your application's lib, WEB-INF/lib, or classpath directories. In Maven projects, examine the dependency tree for the camel-hessian dependency.Affected if The camel-hessian component JAR is present in your deployment.
-
Verify camel-hessian is in useSearch configuration files (XML routes, Java DSL code) for references to 'hessian' in endpoint URIs, or look for bean definitions that instantiate HessianSerializer or HessianFactory.Affected if Your application defines routes or endpoints using the hessian protocol or imports Hessian serialization classes.
-
Inspect deserialization data sourcesExamine your integration flows to determine whether the camel-hessian endpoints receive data from untrusted network sources, external APIs, or user-provided input.Affected if The camel-hessian component processes serialized data from external or untrusted sources.
-
Check for JVM-level serialization filtersInspect JVM startup arguments for -Dj.serial.filter= configuration or look for a java.serial.filter security property in your runtime configuration.Affected if No Java serialization filter is configured at the JVM level to inspect incoming serialized data.
You are affected if you run Apache Camel versions 2.0.0-2.19.3 or 2.20.0, have the camel-hessian component deployed, and use it to deserialize data from untrusted sources without JVM-level serialization filters in place.
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.
dbcve · scoped2.19.42.20.1
Upgrade to Apache Camel 2.19.4 or 2.20.1 or later. If immediate upgrade is not feasible, disable or avoid using the camel-hessian component with untrusted data sources and implement Java serialization filters (j.serial.filter) at the JVM level.
2.19.4 (for 2.19.x line) or 2.20.1 (for 2.20.x line)
- Upgrade Apache Camel from any version >= 2.0.0 and < 2.19.4 to version 2.19.4 or later in the 2.19.x line
- OR upgrade from any version >= 2.20.0 and < 2.20.1 to version 2.20.1 or later in the 2.20.x line
- After upgrading, rebuild and redeploy any applications that use the camel-hessian component
- Verify the upgrade by checking that the camel-hessian library version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Camel
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12633 — 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-12633 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