Dubbo Zookeeper does not check serialization id
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 22%. Fixed in 2.6.9 and 2.7.8.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | >=Apache Dubbo 2.6.x <2.6.9, >=Apache Dubbo 2.7.x <2.7.8 | 2.6.9, 2.7.8 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket