Skip to content
Fencer Vulns
low 2.9

CVE-2024-22371 json

Apache Camel issue on ExchangeCreatedEvent

published 2024-02-26 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-0700 , GHSA-qpxm-689r-3849

cvss
2.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.camel:camel-core 3.21.4, 3.22.1, 4.0.4, 4.4.0
  • Apache Software Foundation Apache Camel 1.x

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-22371 updated cvss 2.9

camel-core: Exposure of sensitive data by crafting a malicious EventFactory

  • Red Hat build of Apache Camel - HawtIO 4 camel-core camel-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-core camel-core
    affected: workaround, no fix available
  • Red Hat build of Apache Camel for Spring Boot 3 camel-core camel-core Red Hat Fuse 7 camel-core camel-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Integration Camel K 1 camel-core camel-core
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Integration Camel Quarkus 2 camel-core camel-core Red Hat JBoss Data Grid 7 camel-core camel-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Process Automation 7 camel-core camel-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Single Sign-On 7 camel-core camel-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat OpenShift Serverless 1.33 openshift-serverless-1/logic-rhel8-operator 1.33.0-3, openshift-serverless-1/logic-operator-bundle 1.33.0-5, openshift-serverless-1/logic-swf-builder-rhel8 1.33.0-5, openshift-serverless-1/logic-swf-devmode-rhel8 1.33.0-5, openshift-serverless-1/logic-data-index-ephemeral-rhel8 1.33.0-5, openshift-serverless-1/logic-data-index-postgresql-rhel8 1.33.0-5, +3 more
    fixed: vendor fix RHSA-2024:4057
show 1 more
  • Red Hat OpenShift Serverless camel-core camel-core Red Hat build of Apache Camel for Spring Boot 4 camel-core camel-core Red Hat Build of Keycloak camel-core camel-core Red Hat JBoss Enterprise Application Platform 7 camel-core camel-core Red Hat JBoss Enterprise Application Platform 8 camel-core camel-core Red Hat JBoss Enterprise Application Platform Expansion Pack camel-core camel-core
    +1 more products
    Red Hat support for Spring Boot camel-core camel-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.9 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 2.9 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-core
>=3.0.0, <3.21.4
>=3.22.0, <3.22.1
>=4.0.0, <4.0.4
>=4.1.0, <4.4.0
3.21.4
3.22.1
4.0.4
4.4.0

Affected products

  • Apache Software Foundation Apache Camel

Classification

Weakness
  • CWE-922 Insecure Storage of Sensitive Information
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.