dbcve.org
DubboApplication · Apache

CVE-2021-30180

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-01
Fix available
A fix is available. Upgrade to 2.7.10 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Apache Dubbo prior to 2.7.9 support Tag routing which will enable a customer to route the request to the right server. These rules are used by the customers when making a request in order to find the right endpoint. When parsing these YAML rules, Dubbo customers may enable calling arbitrary constructors.

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 Dubbo before 2.7.9 contains a vulnerability in its Tag routing feature where parsing of YAML rules allows instantiation of arbitrary constructors. This unsafe deserialization during YAML parsing enables remote code execution by crafting malicious YAML routing rules that trigger instantiation of hostile classes.

MitigationUpgrade Apache Dubbo to version 2.7.9 or later which contains the fix for safe YAML parsing. If immediate upgrade is not possible, disable or restrict the Tag routing feature and implement network-level access controls to limit who can submit routing rules.

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.10

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 Dubbo version
    Locate the Dubbo JAR files or check the application's dependency management (pom.xml, build.gradle, or the compiled dubbo-* jars in the classpath). Run: `grep -r 'dubbo' pom.xml` or list JAR files containing 'dubbo' and note the version number.
    Affected if The installed version is 2.7.0 through 2.7.9 (any version >= 2.7.0 and < 2.7.10)
  2. Verify Tag routing is enabled
    Check Dubbo configuration files (typically in application.yml, dubbo.properties, or Spring XML config) for any 'dubbo:tag-router' or 'tag-router' entries. Also search for references to 'routing' or 'tag' in YAML configuration files.
    Affected if Tag routing feature is configured or enabled in any dubbo configuration files
  3. Inspect YAML routing rule files
    Search for YAML files that define routing rules, typically named with patterns like '*route*.yml', '*routing*.yml', or stored in directories such as 'router' or 'rules'. Look for files containing 'tag' entries under routing configurations.
    Affected if YAML routing rule files exist and contain tag-based routing definitions
  4. Check who can submit routing rules
    Review network access controls and application permissions around any administrative interfaces, APIs, or RPC endpoints that accept routing rule submissions. Check if these endpoints are exposed externally or accessible without authentication.
    Affected if Routing rules can be submitted by unauthenticated or external users

You are affected if you run Dubbo version 2.7.0 through 2.7.9 AND have Tag routing enabled, as this combination allows unsafe YAML deserialization to trigger remote code execution.

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 2.7.10 or later
Fixed in 2.7.10
Interim mitigation

Upgrade Apache Dubbo to version 2.7.9 or later which contains the fix for safe YAML parsing. If immediate upgrade is not possible, disable or restrict the Tag routing feature and implement network-level access controls to limit who can submit routing rules.

Recommended fix High confidence

Apache Dubbo 2.7.10 or later (2.7.x stable)

  1. 1. Identify all applications and services using Apache Dubbo dependency versions between 2.7.0 and 2.7.9
  2. 2. Locate the Maven pom.xml, Gradle build.gradle, or other dependency management files for each affected application
  3. 3. Update the Dubbo version from 2.7.x (where x < 10) to 2.7.10 or later
  4. 4. For Maven projects, change the dubbo dependency version to 2.7.10 or the latest 2.7.x stable release
  5. 5. For Gradle projects, update the Dubbo version similarly
  6. 6. Rebuild and test the application to ensure compatibility
  7. 7. Deploy the updated application to production environments
Caveat Minor: Review release notes for 2.7.10 for any behavior changes; most users should upgrade without issues

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

Fix this in Dubbo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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