dbcve.org
SeataApplication · Apache

CVE-2024-22399

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-16
Fix available
A fix is available. Upgrade to 1.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Seata contains a deserialization vulnerability where attackers can send malicious serialized bytecode directly via the Seata private protocol when authentication is disabled and client SDK dependencies are not used, leading to remote code execution.

MitigationUpgrade to Apache Seata 2.1.0 or 1.8.1, or re-enable authentication on the Seata-Server and ensure Seata client SDK dependencies are in use.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeataApplication
Affected:>= 1.0.0, < 1.8.1= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Apache Seata server version
    Locate the Seata server installation and check its version (typically in a version file, manifest, or pom.xml at the server location). Compare this version against the affected ranges: >= 1.0.0 and < 1.8.1, or exactly 2.0.0.
    Affected if The installed version falls within >= 1.0.0 and < 1.8.1, or is exactly 2.0.0.
  2. Check whether Seata-Server authentication is disabled
    Examine the Seata server configuration file (commonly named application.yml, application.properties, or seata.conf in the server deployment) for the authentication or security configuration section. Determine if authentication has been explicitly disabled or is not configured.
    Affected if Authentication is disabled or not properly configured on the Seata-Server.
  3. Determine if client SDK dependencies are being used
    Inspect the application or service that connects to the Seata server. Check the dependency management file (such as pom.xml, build.gradle, or a lib directory) for the presence of official Seata client SDK libraries.
    Affected if The application does not use official Seata client SDK dependencies, allowing direct protocol access.

You are affected if your Seata server version is 1.0.0 through 1.8.0 or exactly 2.0.0, AND authentication is disabled on the server, AND your applications lack proper Seata client SDK dependencies.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.1 or later
Fixed in 1.8.1
Interim mitigation

Upgrade to Apache Seata 2.1.0 or 1.8.1, or re-enable authentication on the Seata-Server and ensure Seata client SDK dependencies are in use.

Recommended fix High confidence

Upgrade to Seata 1.8.1 (for 1.x line) or 2.1.0 (for 2.x line)

  1. Identify the current Seata version in use by checking pom.xml, build.gradle, or the running Seata server
  2. Stop the Seata server and all connected clients
  3. Download Apache Seata version 1.8.1 (for 1.x users) or 2.1.0 (for 2.x users) from the official Apache Seata release repository
  4. Replace the existing Seata server binaries with the new version
  5. Review and preserve the existing Seata configuration files in the conf directory
  6. Start the Seata server with the upgraded version
  7. Upgrade Seata client SDK dependencies in all connected applications to matching version (1.8.1 or 2.1.0)
  8. Restart all client applications to use the updated dependencies
Caveat Minor: Review release notes for any configuration or API changes between versions; ensure client SDK versions match server version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seata Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22399 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22399 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data