CVE-2021-37579 json
Bypass deserialization checks in Apache Dubbo
published 5y ago modified 4mo ago also GHSA-q897-9jxf-jg9r , EUVD-2021-2100
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.6%
- EPSS 6.6% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
The Dubbo Provider will check the incoming request and the corresponding serialization type of this request meet the configuration set by the server. But there's an exception that the attacker can use to skip the security check (when enabled) and reaching a deserialization operation with native java serialization. Apache Dubbo 2.7.13, 3.0.2 fixed this issue by quickly fail when any unrecognized request was found.
Patch / fix
- maven org.apache.dubbo:dubbo 2.7.13, 3.0.2
- apache dubbo 2.7.13, 3.0.2
Is CVE-2021-37579 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
6.56% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.dubbo:dubbo | <2.7.13 >=3.0.0, <3.0.2 |
2.7.13 3.0.2 |
Affected products
- Apache Software Foundation Apache Dubbo
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
lists.apache.org
/thread.html/r898afa109cdbb4b79724308648ff0718152ebe1d3d6dfc7202d958bc%40%3Cdev.dubbo.apache.org%3E
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-37579
advisory
-
github.com
/apache/dubbo
package
Sources
- CVE List CVE-2021-37579
- GitHub Advisory GHSA-q897-9jxf-jg9r
- NVD CVE-2021-37579
Fencer Intel 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.