Security Digest · Vulnerability record
CVE-2024-22399: Apache Seata Deserialization of Untrusted Data vulnerability
Deserialization of Untrusted Data vulnerability in Apache Seata.
CVSS 9.2 Critical EPSS 3.3% · p88
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 3.3%, percentile 88: FIRST’s model estimates a 3.3% chance of exploitation activity in the next 30 days, higher than 88% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
org.apache.seata:seata-core(Maven) >= 1.0.0, < 1.8.1, fixed in 1.8.1;org.apache.seata:seata-core(Maven) = 2.0.0, fixed in 2.1.0. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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.
Weakness type: CWE-502.
Product: org.apache.seata:seata-core (Maven) · Assigned by: apache · Published: 2024-09-16
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Maven | org.apache.seata:seata-core | >= 1.0.0, < 1.8.1 | 1.8.1 |
| Maven | org.apache.seata:seata-core | = 2.0.0 | 2.1.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Apache Software Foundation | Apache Seata | 2.0.0, 1.0.0 <= 1.8.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADP | 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: present (depends on deployment conditions)
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 3.29% probability of exploitation activity in the next 30 days; percentile 88.
Timeline
- — CVE record last updated
- — CVE record published by apache
- — GitHub-reviewed advisory GHSA-3xq2-w6j4-c99r published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- lists.apache.org lists.apache.org
Vulnerability records
- GitHub Advisory GHSA-3xq2-w6j4-c99r github.com
- CVE.org record CVE-2024-22399 cve.org
- NVD entry CVE-2024-22399 nvd.nist.gov
Other references from the CVE record and advisory
- openwall.com openwall.com