CVE-2021-25641: vulnerability in Apache Dubbo
Dubbo Zookeeper does not check serialization id
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 21%
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 products
Apache Software Foundation · Apache DubboRelated CVEs — Apache Dubbo
In the same product, most dangerous first.
CVE-2021-30181—Apache Dubbo RCE on customers via Script route poisoning (Nashorn script injection)EPSS 60.9%CVE-2021-30180—Apache Dubbo RCE on customers via Condition route poisoning (Unsafe YAML unmarshaling)EPSS 60.3%CVE-2021-43297—Dubbo Hessian cause RCE when parse errorEPSS 17.4%CVE-2023-29234—Bypass serialize checks in Apache DubboEPSS 7.4%CVE-2021-37579—Bypass deserialization checks in Apache DubboEPSS 6.6%CVE-2020-11995—Apache Dubbo default deserialization protocol Hessian2 cause CREEPSS 5.9%