CVE-2024-22369
Published: 20 February 2024
Summary
CVE-2024-22369 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Apache Camel. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 6.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-22369 is a deserialization of untrusted data vulnerability, tracked as CWE-502, in the Apache Camel SQL component. It affects Apache Camel versions from 3.0.0 before 3.21.4, from 3.22.0 before 3.22.1, from 4.0.0 before 4.0.4, and from 4.1.0 before 4.4.0. The flaw carries a CVSS 3.1 score of 7.8 with an attack vector that is local, requires no privileges, and needs user interaction.
An attacker able to supply crafted serialized data to the SQL component can trigger unsafe deserialization, resulting in high impact to confidentiality, integrity, and availability on the affected system.
Apache project advisories direct users to upgrade to 4.4.0 to resolve the issue, to 4.0.4 if remaining on the 4.0.x LTS stream, or to 3.21.4 or 3.22.1 when using 3.x releases. The associated EPSS score has remained near 0.12 with only minor fluctuation between its current and peak values.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0478
Vulnerability details
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…
more
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
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.