CVE-2021-25641
Dubbo Zookeeper does not check serialization id
CRITICAL 9.8EPSS 21.2%
Each Apache Dubbo server will set a serialization id to tell the clients which serialization protocol it is working on. But for Dubbo versions before 2.7.8 or 2.6.9, an attacker can choose which serialization id the Provider will use by tampering with the byte preamble flags, aka, not following the server's instruction. This means that if a weak deserializer such as the Kryo and FST are somehow in code scope (e.g. if Kryo is somehow a part of a dependency), a remote unauthenticated attacker can tell the Provider to use the weak deserializer, and then proceed to exploit it.
- Affected
- Apache Software Foundation · Apache Dubbo
- CVSS v3.1 NVD
- 9.8 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS v2.0 NVD
- 7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P - EPSS
- 21.22% chance of exploitation in the next 30 days, 98th percentile
- Published
- 2021-05-29
- Updated
- 2024-08-03
Proof-of-concept exploits (2)
- Dor-Tumarkin/CVE-2021-25641-Proof-of-Concept52★ · 2021-06-06
- l0n3rs/CVE-2021-256414★ · 2022-11-10
Security advisories
- https://lists.apache.org/thread.html/r99ef7fa35585d3a68762de07e8d2b2bc48b8fa669a03e8d84b9…
- advisories/GHSA-v2rg-8cwr-75g8