dbcve.org
DubboApplication · Apache

CVE-2021-30181

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-01
Fix available
A fix is available. Upgrade to 2.6.10 / 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.6.9 and 2.7.9 supports Script 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 rules, Dubbo customers use ScriptEngine and run the rule provided by the script which by default may enable executing arbitrary code.

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's script routing feature uses Java's ScriptEngine to execute customer-supplied routing rules without proper sandboxing. An attacker can inject malicious scripts through routing rules to achieve arbitrary remote code execution on the Dubbo server, as the ScriptEngine executes code provided in the routing configuration.

MitigationUpgrade Apache Dubbo to version 2.6.9, 2.7.9, or later which contains the security fix. If upgrading is not immediately feasible, disable the script routing feature entirely or implement network-level controls to restrict access to the routing configuration interface.

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.5.0, < 2.6.10>= 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 build configuration (pom.xml, build.gradle) and note the installed version number.
    Affected if The version falls within >= 2.5.0 and < 2.6.10, or >= 2.7.0 and < 2.7.10.
  2. Check for routing configuration files
    Search the Dubbo configuration directory or application resources for routing rule files, typically named with 'route' or 'routing' in the filename, or stored in a routing configuration store.
    Affected if Any routing configuration files exist in the Dubbo environment.
  3. Verify if script routing is in use
    Examine the routing configuration files for entries using the 'script' type or JavaScript/Groovy execution, or inspect the Dubbo admin console or API for active routing rules of type 'script'.
    Affected if Routing rules with script type (script, javascript, groovy) are defined or active.
  4. Confirm ScriptEngine usage in routing
    Review the routing implementation or configuration to verify that the Java ScriptEngine is being invoked to execute routing scripts.
    Affected if The routing feature uses Java's ScriptEngine to evaluate routing scripts.

The environment is affected if Dubbo version is within the vulnerable ranges AND script routing is enabled with routing rules configured to execute scripts via ScriptEngine.

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.6.10 / 2.7.10 or later
Fixed in 2.6.102.7.10
Interim mitigation

Upgrade Apache Dubbo to version 2.6.9, 2.7.9, or later which contains the security fix. If upgrading is not immediately feasible, disable the script routing feature entirely or implement network-level controls to restrict access to the routing configuration interface.

Recommended fix High confidence

Dubbo 2.6.10 (for 2.6.x users) or Dubbo 2.7.10 (for 2.7.x users)

  1. Identify your current Dubbo version (2.5.x, 2.6.x, or 2.7.x)
  2. If using 2.6.x line: upgrade to Dubbo version 2.6.10 or later
  3. If using 2.7.x line: upgrade to Dubbo version 2.7.10 or later
  4. After upgrade, test that script routing functionality still works as expected
  5. Review any custom script routing rules for compatibility with the fixed version

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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