CVE-2024-42323
Published: 21 September 2024
Summary
CVE-2024-42323 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Apache Hertzbeat. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 1.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Apache HertzBeat versions prior to 1.6.0 contain a deserialization vulnerability in the SnakeYAML component that permits loading of malicious XML input. The flaw is tracked as CVE-2024-42323 and is associated with CWE-502, allowing untrusted data to be processed during deserialization in the affected monitoring application.
Authenticated attackers with network access can exploit the issue at low complexity to achieve remote code execution, resulting in complete loss of confidentiality, integrity, and availability according to the CVSS 3.1 score of 8.8. The vulnerability is restricted to authorized users and does not affect unauthenticated or anonymous access paths.
Project advisories direct users to upgrade to HertzBeat 1.6.0, which contains the fix, and reference notifications issued through Apache mailing lists and the OSS-Security distribution for coordinated disclosure. The associated EPSS score has remained at 0.7555 without material increase since publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-39551
Vulnerability details
SnakeYaml Deser Load Malicious xml rce vulnerability in Apache HertzBeat (incubating). This vulnerability can only be exploited by authorized attackers. This issue affects Apache HertzBeat (incubating): before 1.6.0. Users are recommended to upgrade to version 1.6.0, which fixes the issue.
- 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.