CVE-2024-22371: Apache Camel issue on ExchangeCreatedEvent

Published Feb 23, 2024
·
Updated

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.0.0 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.

Other sources

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.

MITRE

Affected Software

8 affected componentsFixes available
maven/org.apache.camel:camel-core>=3.0.0<3.21.4
3.21.4
maven/org.apache.camel:camel-core>=4.1.0<4.4.0
4.4.0
maven/org.apache.camel:camel-core>=4.0.0<4.0.4
4.0.4
maven/org.apache.camel:camel-core=3.22.0
3.22.1
Apache Camel>=3.0.0<3.21.4
Apache Camel>=4.0.0<4.0.4
Apache Camel>=4.1.0<4.4.0
Apache Camel=3.22.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 3.21.4
  2. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 4.4.0
  3. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 4.0.4
  4. Upgrade

    Upgrade maven/org.apache.camel:camel-core to a version that resolves this vulnerability.

    Fixed in 3.22.1
  5. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 3.21.4
  6. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 3.22.1
  7. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.0.4
  8. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.4.0

Event History

Feb 26, 2024
CVE Published
via MITRE·09:22 AM
Data Sourced
via MITRE·09:22 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·11:04 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:27 PM
Affected Software
Advisory Published
via GitHub·06:30 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22371?

CVE-2024-22371 has been classified as a medium severity vulnerability due to the potential exposure of sensitive data.

2

How do I fix CVE-2024-22371?

To fix CVE-2024-22371, update to Apache Camel version 3.21.4, 3.22.1, 4.0.4, or 4.4.0.

3

What systems are affected by CVE-2024-22371?

CVE-2024-22371 affects Apache Camel versions from 3.0.0 through 3.21.3, 3.22.X through 3.22.0, and 4.0.X through 4.0.3.

4

What kind of data is exposed by CVE-2024-22371?

CVE-2024-22371 can lead to the exposure of sensitive data when a malicious EventFactory is crafted.

5

Is there a workaround for CVE-2024-22371?

There is no recommended workaround for CVE-2024-22371 aside from applying the necessary updates to affected versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203