Deserialization in Apache Dubbo
CVE-2021-25641
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.216, 97.7th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Apache Dubbo
- Apache Software Foundation Dubbo — versions Apache Dubbo 2.7.x, Apache Dubbo 2.6.x
Weakness classification (CWE)
Public exploits and proof-of-concept code
2 public repositories with exploit or proof-of-concept code for this CVE:
- Dor-Tumarkin/CVE-2021-25641-Proof-of-Concept (52 stars, last pushed 2021-06-06): Apache/Alibaba Dubbo <= 2.7.3 PoC Code for CVE-2021-25641 RCE via Deserialization of Untrusted Data; Affects Versions <= 2.7.6 With Different Gadgets
- l0n3rs/CVE-2021-25641 (4 stars, last pushed 2022-11-10): A Exploit Tool For CVE-2021-25641.
Also mentioned in 22 other repositories (AdeliaNitzsche/Java-Deserialization-Cheat-Sheet, Armandhe-China/ApacheDubboSerialVuln, ARPSyndicate/cvemon, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- lists.apache.org/thread.html/r99ef7fa35585d3a68762de07e8d2b2bc48b8fa669a03e8d84… (Mailing List, Vendor Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.