dbcve.org
CamelApplication · Apache

CVE-2024-22369

HIGH · 7.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 →
81/100
Remediation priority · High
No privileges

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 SQL ComponentThis 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

This is a deserialization of untrusted data vulnerability in Apache Camel SQL Component. The vulnerability allows attackers to potentially execute arbitrary code or cause denial of service by supplying malicious serialized data to the SQL component's deserialization endpoints.

MitigationUpgrade Apache Camel to version 4.4.0, or to 4.0.4 for 4.0.x LTS users, or to 3.21.4/3.22.1 for 3.x users. If immediate upgrade is not possible, avoid using the SQL component with untrusted data sources.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Apache Camel version
    Inspect your project's pom.xml, build.gradle, or runtime dependencies for the camel-core or camel-sql artifact version. If running a deployed application, check the JAR manifest or classpath for org.apache.camel version.
    Affected if Installed version falls within 3.0.0 to 3.21.3, 3.22.0, 4.0.0 to 4.0.3, or 4.1.0 to 4.3.0 range
  2. Identify if camel-sql component is in use
    Search project dependencies for the camel-sql library (org.apache.camel:camel-sql). Check route definitions in Java, XML, or YAML configuration files for sql: endpoints.
    Affected if camel-sql component is present in dependencies and used in any route definition
  3. Check SQL component data source exposure
    Review the SQL component configuration for dataSource or dataSourceRef references. Determine whether connected databases or query inputs originate from untrusted or external sources.
    Affected if SQL component connects to databases with untrusted query input or deserializes data from untrusted sources
  4. Inspect deserialization usage in SQL routes
    Examine SQL route configurations for any use of serialization/deserialization features, custom type converters handling Java objects, or integration with external systems that supply serialized payloads.
    Affected if SQL routes accept or process serialized Java objects from external or untrusted inputs

You are affected if your Apache Camel version is within the vulnerable ranges AND the SQL component is actively processing untrusted data through deserialization endpoints.

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 Apache Camel to version 4.4.0, or to 4.0.4 for 4.0.x LTS users, or to 3.21.4/3.22.1 for 3.x users. If immediate upgrade is not possible, avoid using the SQL component with untrusted data sources.

Recommended fix High confidence

Upgrade to 4.4.0 (recommended) or 3.21.4/3.22.1/4.0.4 based on current version branch

  1. 1. Identify the current Apache Camel version in use by checking pom.xml or dependency management files
  2. 2. Based on current version, determine the appropriate upgrade target: if on 3.x (except 3.21.4 or 3.22.1), upgrade to 3.21.4 or 3.22.1; if on 4.0.0-4.0.3, upgrade to 4.0.4; if on 4.1.0-4.3.x, upgrade to 4.4.0
  3. 3. Update the Camel version in Maven pom.xml or build configuration to the chosen fixed version
  4. 4. Rebuild the application and run all tests to verify compatibility
  5. 5. Deploy the updated application
Caveat Review Camel migration guides when upgrading across major versions (e.g., 3.x to 4.x) as API changes may require code adjustments

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

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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