Deserialization in Apache Seata
CVE-2024-22399
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 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.
Vulnerability class: Insecure Deserialization
EPSS: 0.033 (87.2th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Apache Seata — versions 2.0.0
- Apache Software Foundation Seata — versions 2.0.0, 1.0.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security@apache.org (vendor-advisory, Mailing List, Vendor Advisory)
- af854a3a-2127-422b-91ae-364da2661108
Frequently asked questions
- What is CVE-2024-22399?
- CVE-2024-22399 is a critical-severity vulnerability in Apache Seata, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2024-09-16.
- How severe is CVE-2024-22399?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2024-22399 known to be exploited?
- 14 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.