Vulnerabilities in pkg:maven/org.apache.seata/seata-core

PACKAGE
Advisory Identifier: GHSA-3xq2-w6j4-c99r
Advisory Summary

CVE-2024-22399 is a CRITICAL (CVSS 8.1) apache seata deserialization of untrusted vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Seata core libraries in the Maven ecosystem. The issue involves apache seata deserialization of untrusted data vulnerability. Remediation is available by upgrading affected packages to version 2.1.0, 1.8.1.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.apache.seata/seata-core

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.apache.seata/seata-core. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-3xq2-w6j4-c99r CVE-2024-22399 CRITICAL Apache Seata Deserialization of Untrusted Data vulnerability

CVE-2024-22399 at a Glance

CVE Identifier CVE-2024-22399
GHSA Identifier GHSA-3xq2-w6j4-c99r
Severity CRITICAL
CVSS v3.1 Base Score 8.1
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Seata core
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2024-22399

To remediate this vulnerability, upgrade all affected Seata core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.apache.seata:seata-core fixed: 2.1.0
<dependency>
    <groupId>org.apache.seata</groupId>
    <artifactId>seata-core</artifactId>
    <version>2.1.0</version>
</dependency>
org.apache.seata:seata-core fixed: 1.8.1
<dependency>
    <groupId>org.apache.seata</groupId>
    <artifactId>seata-core</artifactId>
    <version>1.8.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.apache.seata

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2024-22399, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.apache.seata

Analyze the terminal output to locate any version of Seata core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.apache.seata command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Seata core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2024-22399 Affected Seata core Versions

2 component(s)
Fixed Versions:
2.1.01.8.1
Product / Package Ecosystem Affected Versions Fixed Version
org.apache.seata:seata-core
Maven
≥ 2.0.0
< 2.1.0
All 1 versions
2.0.0
2.1.0
org.apache.seata:seata-core
Maven
≥ 1.0.0
< 1.8.1
1.8.1

References

Frequently Asked Questions

What is CVE-2024-22399?
CVE-2024-22399 is a security vulnerability in Seata core involving Apache Seata Deserialization of Untrusted Data vulnerability under CWE-502: Deserialization of Untrusted Data.
Which Seata core versions are affected?
Affected versions include releases prior to 2.1.0, 1.8.1 across affected packages: org.apache.seata:seata-core.
What version fixes CVE-2024-22399?
Upgrading to 2.1.0, 1.8.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is seata-core affected?
Yes, org.apache.seata:seata-core is affected in releases prior to 2.1.0, 1.8.1. Upgrade your dependency to 2.1.0, 1.8.1 or later.
What is the CVSS score of CVE-2024-22399?
CVE-2024-22399 has a CVSS v3.1 base score of 8.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2024-22399?
CVE-2024-22399 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check Maven dependencies for CVE-2024-22399?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.seata'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3xq2-w6j4-c99r",
  "modified" : "2024-11-18T16:27:12Z",
  "published" : "2024-09-16T14:37:28Z",
  "aliases" : [ "CVE-2024-22399" ],
  "summary" : "Apache Seata Deserialization of Untrusted Data vulnerability",
  "details" : "Deserialization of Untrusted Data vulnerability in Apache Seata. \n\nWhen 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.\n\nThis issue affects Apache Seata: 2.0.0, from 1.0.0 through 1.8.0.\n\nUsers are recommended to upgrade to version 2.1.0/1.8.1, which fixes the issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.seata:seata-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.1.0"
      } ]
    } ],
    "versions" : [ "2.0.0" ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.seata:seata-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "fixed" : "1.8.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-22399"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apache/incubator-seata"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/91nzzlxyj4nmks85gbzwkkjtbmnmlkc4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-09-16T20:18:41Z",
    "nvd_published_at" : "2024-09-16T12:15:02Z"
  }
}