DubboApplication · Apache
CVE-2019-17564
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 · uneditedUnsafe deserialization occurs within a Dubbo application which has HTTP remoting enabled. An attacker may submit a POST request with a Java object in it to completely compromise a Provider instance of Apache Dubbo, if this instance enables HTTP. This issue affected Apache Dubbo 2.7.0 to 2.7.4, 2.6.0 to 2.6.7, and all 2.5.x 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 confidenceApache Dubbo contains an unsafe deserialization vulnerability in its HTTP remoting implementation. When HTTP remoting is enabled, attackers can send a POST request containing a malicious serialized Java object that gets deserialized without proper validation, leading to remote code execution and complete compromise of the Dubbo Provider instance.
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
>= 2.5.0, <= 2.5.10>= 2.6.0, <= 2.6.7>= 2.7.0, <= 2.7.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Dubbo versionCheck your application's dependencies (Maven pom.xml, Gradle build file, or JAR manifest) for the dubbo version, or run 'grep -r "dubbo"' in your lib/dependencies directoryAffected if The version falls within 2.5.0-2.5.10, 2.6.0-2.6.7, or 2.7.0-2.7.4
-
Determine if HTTP remoting is enabledSearch Dubbo configuration files (dubbo.properties, dubbo.xml, application.yml) for 'dubbo.protocol.name=http' or check for HTTP transport configuration in the provider settingsAffected if HTTP protocol (dubbo.protocol.name=http) is explicitly configured as the remoting protocol
-
Verify HTTP port exposureCheck network configuration for port 8080 or the configured HTTP port, or review firewall rules and container network settingsAffected if The Dubbo HTTP endpoint is accessible from untrusted network segments
-
Inspect deserialization configurationReview Dubbo provider configuration for any existing SerializationConfig or ObjectInput filters, check if Hessian or Java serialization is in useAffected if No custom ObjectInput filter is configured and Hessian or Java deserialization is used for the HTTP endpoint
You are affected if your Dubbo version is within the vulnerable ranges AND HTTP remoting is enabled and exposed, allowing unauthenticated attackers to send malicious serialized payloads to your HTTP endpoint.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Apache Dubbo to version 2.7.5+, 2.6.8+, or later which contains the fix. If immediate patching is not possible, disable HTTP remoting or implement network-level restrictions to prevent external access to the Dubbo HTTP endpoint.
Dubbo 2.7.5 or later (or 2.6.8+/2.5.11+ depending on your major version branch)
- Identify the current Dubbo version in use by checking project dependencies (pom.xml, build.gradle, or equivalent)
- For Dubbo 2.5.x users: upgrade to version 2.5.11 or later
- For Dubbo 2.6.x users: upgrade to version 2.6.8 or later
- For Dubbo 2.7.x users: upgrade to version 2.7.5 or later (recommended: latest 2.7.x stable release)
- Update the version in build configuration files (pom.xml, build.gradle, etc.)
- Rebuild and redeploy the application
- Verify that HTTP remoting is only enabled when necessary; consider disabling it if not required for the application's functionality
- Test the application thoroughly after upgrade to ensure compatibility
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
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 locallyCheck whether your project pulls in CVE-2019-17564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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