CVE-2019-17564 in the critical feed json
Deserialization of Untrusted Data in Apache Dubbo
published 2020-04-01 6 y ago modified 2026-06-17 4 mo ago also GHSA-69wp-3pm3-hxgg , EUVD-2022-2765
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 36.5%
- EPSS 36.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
Unsafe 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.
Patch / fix
- maven org.apache.dubbo:dubbo-rpc-http-invoker 2.7.5
Exploit prediction
36.51% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Apache Dubbo 2.5.x-2.7.4 - Insecure Deserialization nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.dubbo:dubbo-rpc-http-invoker | >=2.5.0, <2.7.5 |
2.7.5 |
Affected products
- Apache Apache Dubbo
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/apache/dubbo/commit/9b18fe228971eaeca9b87d7b7e95df1c2a8ff91b
web
-
lists.apache.org
/thread.html/r13f7a58fa5d61d729e538a378687118e00c3e229903ba1e7b3a807a2%40%3Cdev.dubbo.apache.org%3E
web, mailing-list, vendor-advisory
-
advisory.checkmarx.net
/advisory/CX-2020-4275
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-17564
advisory
-
github.com
/apache/dubbo/releases/tag/dubbo-2.7.5
web
Sources
- CVE List CVE-2019-17564
- GitHub Advisory GHSA-69wp-3pm3-hxgg
- NVD CVE-2019-17564
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.