CVE-2024-22399
Published: 16 September 2024
Summary
CVE-2024-22399 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Apache Seata. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 1.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Apache Seata versions 2.0.0 and 1.0.0 through 1.8.0 contain a deserialization of untrusted data vulnerability (CWE-502) with a CVSS 3.1 score of 9.8. The flaw resides in the Seata-Server component and is triggered when authentication is disabled and the official client SDK is not used, allowing direct submission of serialized payloads over the Seata private protocol.
An unauthenticated remote attacker can craft and send malicious bytecode that the server deserializes without validation. Successful exploitation grants the attacker the ability to execute arbitrary code, resulting in full confidentiality, integrity, and availability impact on the affected server.
Apache has published mitigation guidance in its security advisories recommending immediate upgrade to Seata 2.1.0 or 1.8.1. The current and peak EPSS scores both stand at 0.7829, indicating sustained exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2706
Vulnerability details
Deserialization of Untrusted Data vulnerability in Apache Seata. When developers disable authentication on the Seata-Server and do not use the Seata client SDK dependencies, they may construct uncontrolled serialized malicious requests by directly sending bytecode based on the Seata private…
more
protocol. This issue affects Apache Seata: 2.0.0, from 1.0.0 through 1.8.0. Users are recommended to upgrade to version 2.1.0/1.8.1, 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.