dbcve.org
DubboApplication · Apache

CVE-2022-24969

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to 2.6.12 / 2.7.15 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
bypass CVE-2021-25640 > In Apache Dubbo prior to 2.6.12 and 2.7.15, the usage of parseURL method will lead to the bypass of the white host check which can cause open redirect or SSRF vulnerability.

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

In Apache Dubbo prior to versions 2.6.12 and 2.7.15, the parseURL method improperly handles host validation, allowing attackers to bypass the whitelist protection originally implemented for CVE-2021-25640. This enables open redirect or SSRF attacks by manipulating URL parsing to access unauthorized hosts.

MitigationUpgrade Apache Dubbo to version 2.6.12, 2.7.15, or later. If immediate upgrade is not possible, implement additional input validation on user-supplied URLs before passing them to parseURL.

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.6.12>= 2.7.0, < 2.7.15

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed Dubbo version
    Locate the Dubbo library JAR file or dependency declaration in your project (pom.xml, build.gradle, or in the lib directory). Check the file version or dependency version number.
    Affected if The version is less than 2.6.12, or greater than or equal to 2.7.0 but less than 2.7.15.
  2. Locate parseURL usage in codebase
    Search source code for calls to parseURL method, particularly from the Dubbo URL parsing classes. Look for imports or references to com.alibaba.dubbo.common.URL or org.apache.dubbo.common.url.
    Affected if The parseURL method is being called to process URLs in your application code.
  3. Determine if whitelist filtering is in use
    Search for any host whitelist or blacklist configuration related to Dubbo URL processing. Look for configuration parameters named 'host', 'whitelist', or similar access control settings passed to URL parsing.
    Affected if A whitelist was configured to restrict hosts (as mitigation for CVE-2021-25640) and user-supplied URLs can reach the parseURL method.
  4. Check if URLs are user-controlled
    Audit the code path leading to parseURL calls. Determine whether any URL parameters, headers, or body content originate from external user input.
    Affected if External or untrusted input can influence the URL being parsed without additional validation.

You are affected if your Dubbo version falls in the vulnerable range AND your application uses parseURL to process user-supplied URLs without additional validation beyond the bypassed whitelist.

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.12 / 2.7.15 or later
Fixed in 2.6.122.7.15
Interim mitigation

Upgrade Apache Dubbo to version 2.6.12, 2.7.15, or later. If immediate upgrade is not possible, implement additional input validation on user-supplied URLs before passing them to parseURL.

Recommended fix High confidence

Dubbo 2.6.12+ or 2.7.15+ (depending on your major version branch)

  1. Identify current Dubbo version by examining pom.xml or build configuration files
  2. If using Dubbo 2.6.x: upgrade to version 2.6.12 or later
  3. If using Dubbo 2.7.x: upgrade to version 2.7.15 or later
  4. Update the version in pom.xml or build configuration (e.g., change dubbo.version from 2.7.14 to 2.7.15)
  5. Run dependency resolution to confirm the correct version is pulled
  6. Rebuild and redeploy the application
  7. Verify the parseURL method now properly enforces host whitelist checking
Caveat Review release notes for any breaking changes between your current version and the target version, particularly when crossing major version boundaries

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

Fix this in Dubbo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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