dbcve.org
CamelApplication · Apache

CVE-2024-23114

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 3.21.4 / 4.0.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
Deserialization of Untrusted Data vulnerability in Apache Camel CassandraQL Component AggregationRepository which is vulnerable to unsafe deserialization. Under specific conditions it is possible to deserialize malicious payload.This issue affects Apache Camel: from 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0. Users are recommended to upgrade to version 4.4.0, which fixes the issue. If users are on the 4.0.x LTS releases stream, then they are suggested to upgrade to 4.0.4. If users are on 3.x, they are suggested to move to 3.21.4 or 3.22.1

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 confidence

Apache Camel CassandraQL Component's AggregationRepository is vulnerable to unsafe deserialization, allowing remote code execution when deserializing malicious payloads. This critical flaw affects multiple versions across the 3.x and 4.x branches of the integration framework.

MitigationUpgrade to Apache Camel 4.4.0 (or 4.0.4 for LTS, 3.21.4/3.22.1 for 3.x) to resolve the unsafe deserialization. If immediate upgrade is not feasible, disable or avoid using the CassandraQL AggregationRepository component.

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:>= 3.0.0, < 3.21.4>= 4.0.0, < 4.0.4>= 4.1.0, < 4.4.0= 3.22.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.1/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 camel-core version in your project's pom.xml, MANIFEST.MF inside the camel-core JAR, or query the runtime MBean (org.apache.camel:type=context) via JMX console
    Affected if Version is less than 3.21.4, or 4.0.0 to 4.0.3, or 4.1.0 to 4.3.x, or exactly 3.22.0 (these ranges contain the vulnerability)
  2. Locate CassandraQL component dependency
    Search pom.xml for 'camel-cassandraql' dependency, or list JARs in your classpath for 'camel-cassandraql*.jar', or inspect deployed libraries in your application lib folder
    Affected if The camel-cassandraql component is present in the dependencies (vulnerable code is available)
  3. Check for AggregationRepository configuration
    Search source code and configuration files for 'AggregationRepository' bean definitions, or search for XML/DSL routes using 'aggregation' with CassandraQL endpoints
    Affected if AggregationRepository is configured or used with the CassandraQL component (the vulnerable code path is active)
  4. Verify serialization usage in aggregation
    Inspect the AggregationRepository implementation class for ObjectInputStream or untrusted deserialization patterns, or review logs for serialization errors during aggregation operations
    Affected if The aggregation logic deserializes data from untrusted sources without validation (exploitation condition present)

You are affected if your Apache Camel version is within the vulnerable ranges AND the CassandraQL AggregationRepository component is deployed and actively used in your application.

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 3.21.4 / 4.0.4 / 4.4.0 or later
Fixed in 3.21.44.0.44.4.0
Interim mitigation

Upgrade to Apache Camel 4.4.0 (or 4.0.4 for LTS, 3.21.4/3.22.1 for 3.x) to resolve the unsafe deserialization. If immediate upgrade is not feasible, disable or avoid using the CassandraQL AggregationRepository component.

Recommended fix High confidence

Upgrade to 4.4.0 (latest fixed release); for 4.0.x LTS users upgrade to 4.0.4; for 3.x users upgrade to 3.21.4 or 3.22.1

  1. 1. Identify the current Apache Camel version in use by checking project dependencies (pom.xml, build.gradle, or similar)
  2. 2. Determine the appropriate upgrade path based on current version and release stream (LTS vs main)
  3. 3. Update the Camel dependency version in the build configuration to the recommended fixed version
  4. 4. Rebuild the project to ensure dependency resolution completes successfully
  5. 5. Run existing integration and unit tests, particularly any tests involving CassandraQL AggregationRepository
  6. 6. Verify the application starts correctly and the vulnerable component functions as expected
Caveat Minor API or behavior changes possible between major versions; review Camel migration guides if upgrading across major version boundaries (3.x to 4.x)

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

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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