CVE-2024-22399 Apache Seata: Remote Code Execution vulnerability via Hessian Deserialization in Apache Seata Server

Critical 9.8 Published 16 Sep 2024 Updated 16 Sep 2024

Attackers can achieve remote code execution by sending malicious serialized requests if authentication is disabled on the Seata Server.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2024-22399?

CVE-2024-22399 is a critical unsafe deserialization vulnerability in Apache Seata, published on 16 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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: CWE-502

Which versions are affected by CVE-2024-22399?

4 open source packages ship an affected version, including org.apache.seata:seata-core. It affects 1 product.

Package	Affected	Fixed in
`org.apache.seata:seata-core` Maven	From `1.0.0`	`1.8.1`
`org.apache.seata:seata-core` Maven	From `1.0.0`	`1.8.1`
`org.apache.seata:seata-core` Maven	From `2.0.0`	`2.1.0`
`org.apache.seata:seata-core` Maven	From `2.0.0`	`2.1.0`

Products include Apache Seata.

How do I fix CVE-2024-22399?

Upgrade org.apache.seata:seata-core to a fixed version for your release line: 1.8.1 or 2.1.0.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2024-22399 being exploited?

There is no known exploitation of CVE-2024-22399 in the wild and no public exploit code.

Sources

Also known as GHSA-3xq2-w6j4-c99r.