dbcve.org
DubboApplication · Apache

CVE-2022-39198

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to after 3.0.11 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
A deserialization vulnerability existed in dubbo hessian-lite 3.2.12 and its earlier versions, which could lead to malicious code execution. This issue affects Apache Dubbo 2.7.x version 2.7.17 and prior versions; Apache Dubbo 3.0.x version 3.0.11 and prior versions; Apache Dubbo 3.1.x version 3.1.0 and prior versions.

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

A deserialization vulnerability exists in dubbo hessian-lite versions 3.2.12 and earlier that allows malicious code execution through crafted serialized payloads. This affects Apache Dubbo 2.7.x (≤2.7.17), 3.0.x (≤3.0.11), and 3.1.x (≤3.1.0) which depend on the vulnerable hessian-lite library for data serialization.

MitigationUpgrade dubbo hessian-lite to version 3.2.13 or later, or upgrade Apache Dubbo to versions beyond those affected (2.7.18+, 3.0.12+, 3.1.1+) to include the patched hessian-lite dependency.

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
DubboApplication
Affected:>= 2.7.0, <= 2.7.17>= 3.0.0, <= 3.0.11= 3.1.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 Apache Dubbo installation
    Search for dubbo-core JAR files or check Maven/Gradle dependencies for 'dubbo' artifacts. On Linux, run: find / -name 'dubbo*.jar' 2>/dev/null | head -20
    Affected if No Dubbo JARs or dependencies found means not affected
  2. Determine Dubbo version
    Check the dubbo-core or dubbo-dependencies pom.xml/version info, or run: jar -xf dubbo.jar META-INF/MANIFEST.MF && cat META-INF/MANIFEST.MF. In Maven projects, run: mvn dependency:tree | grep dubbo
    Affected if Version falls within 2.7.0-2.7.17, 3.0.0-3.0.11, or 3.1.0 indicates potentially affected
  3. Check hessian-lite library version
    Examine the nested hessian-lite JAR within Dubbo or check Maven/Gradle dependency tree for 'hessian-lite' version. Run: jar -tf dubbo.jar | grep hessian-lite, then extract and check that JAR's version
    Affected if hessian-lite version 3.2.12 or earlier indicates vulnerable library
  4. Confirm Hessian serialization is in use
    Check Dubbo configuration files (dubbo.properties, application.yml) for serialization settings. Look for 'hessian' in serialization protocol config or default SerializationOptimizer implementations
    Affected if Hessian serialization protocol is explicitly configured or remains at default settings indicates the vulnerable code path is active

Environment is affected if Apache Dubbo versions 2.7.0-2.7.17, 3.0.0-3.0.11, or 3.1.0 are running with hessian-lite 3.2.12 or earlier and Hessian serialization is in use (default).

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 a release after 3.0.11
Interim mitigation

Upgrade dubbo hessian-lite to version 3.2.13 or later, or upgrade Apache Dubbo to versions beyond those affected (2.7.18+, 3.0.12+, 3.1.1+) to include the patched hessian-lite dependency.

Recommended fix High confidence

Upgrade to Dubbo 2.7.18+/3.0.12+/3.1.1+ (which include hessian-lite 3.2.13+)

  1. 1. Identify the Dubbo version currently in use by checking project dependencies (pom.xml, build.gradle, or similar)
  2. 2. For Dubbo 2.7.x users: upgrade to Dubbo 2.7.18 or later
  3. 3. For Dubbo 3.0.x users: upgrade to Dubbo 3.0.12 or later
  4. 4. For Dubbo 3.1.x users: upgrade to Dubbo 3.1.1 or later
  5. 5. Verify the hessian-lite dependency is updated to version 3.2.13 or later in the dependency tree
  6. 6. Test the upgrade in a staging environment before production deployment
Caveat Review Dubbo release notes for breaking changes between current and target version; minor version upgrades typically have minimal breaking changes

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

Fix this in Dubbo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39198 — 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-2022-39198 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