dbcve.org
CamelApplication · Apache

CVE-2024-22371

HIGH · 7.5 CVSS v3.1 Published 2024-02-26
Fix available
A fix is available. Upgrade to 3.21.4 / 4.0.4 or later.
See remediation →
84/100
Remediation priority · High
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
Exposure of sensitive data by by crafting a malicious EventFactory and providing a custom ExchangeCreatedEvent that exposes sensitive data. Vulnerability in Apache Camel.This issue affects Apache Camel: from 3.21.X through 3.21.3, from 3.22.X through 3.22.0, from 4.0.X through 4.0.3, from 4.X through 4.3.0. Users are recommended to upgrade to version 3.21.4, 3.22.1, 4.0.4 or 4.4.0, which fixes the issue.

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

This is an information disclosure vulnerability in Apache Camel where a malicious EventFactory can be crafted to provide a custom ExchangeCreatedEvent that exposes sensitive data during message processing. An attacker could exploit this by supplying a specially constructed EventFactory to leak confidential information from exchanges.

MitigationUpgrade Apache Camel to version 3.21.4, 3.22.1, 4.0.4, or 4.4.0 or later to resolve the vulnerability.

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
None
Availability
None

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

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 installed Apache Camel version
    Locate the camel-core JAR file in your deployment and check its version, or run: mvn dependency:tree | grep camel-core, or check your dependency management file (pom.xml, build.gradle) for the camel-core version
    Affected if The installed version falls within any of these ranges: >= 3.0.0 and < 3.21.4; = 3.22.0; >= 4.0.0 and < 4.0.4; >= 4.1.0 and < 4.4.0
  2. Identify if custom EventFactory is in use
    Search your codebase for any class implementing org.apache.camel.spi.EventFactory, or search for EventFactory bean definitions in Spring/Blueprint XML files or @Bean methods
    Affected if A custom or third-party EventFactory implementation is configured and loaded by the Camel runtime
  3. Check for event consumer/listener configurations
    Search for org.apache.camel.spi.EventNotifier or org.apache.camel.api.EventConsumer implementations, and examine any event listening configuration in your route definitions
    Affected if Custom event notification consumers are configured that could receive ExchangeCreatedEvent objects
  4. Verify event exposure in routes
    Inspect Camel route definitions for usage of .onExchangeCreated() or similar event consumer APIs, and review any code that handles exchange lifecycle events
    Affected if Routes contain event consumers that process ExchangeCreatedEvent and could receive data from a malicious EventFactory
  5. Review dependencies for vulnerable camel-core
    Run: mvn dependency:list | grep camel-core (Maven) or gradle dependencies | grep camel-core (Gradle) to confirm the exact version of camel-core in your runtime classpath
    Affected if The camel-core dependency resolves to a version listed in the affected version ranges

You are affected if your Apache Camel version is within any of the vulnerable ranges AND your application uses custom EventFactory or event notification/listener components that can be manipulated to expose exchange data.

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 3.21.4, 3.22.1, 4.0.4, or 4.4.0 or later to resolve the vulnerability.

Recommended fix High confidence

Upgrade to Apache Camel 3.21.4, 3.22.1, 4.0.4, or 4.4.0 (choose the minor version closest to your current version)

  1. Identify your current Apache Camel version in your project's build configuration (pom.xml for Maven or build.gradle for Gradle)
  2. Locate the Camel dependency declaration (e.g., org.apache.camel:camel-api or org.apache.camel:camel-core)
  3. Update the version attribute to one of the fixed versions: 3.21.4, 3.22.1, 4.0.4, or 4.4.0
  4. Run 'mvn clean compile' (Maven) or './gradlew build' (Gradle) to download the new dependency and verify compilation succeeds
  5. Execute your full test suite to confirm the upgrade does not break existing functionality
  6. Redeploy your application with the updated dependency
Caveat Review Camel release notes for your target version; major upgrades (e.g., 3.x to 4.x) may have breaking API changes requiring 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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