Dubbo Zookeeper does not check serialization id
Apache Software Foundation Apache Dubbo
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.dubbo:dubbo Maven |
|
|
| com.alibaba:dubbo Maven |
|
|
Apache Software Foundation Apache Dubbo
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.dubbo:dubbo Maven |
|
|
| com.alibaba:dubbo Maven |
|
|
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.
From the CVE record · apache
Affected Apache Dubbo Providers allow a client to override the server's serialization choice by tampering with byte preamble flags. If a weak deserializer such as Kryo or FST is in code scope, a remote unauthenticated attacker can make the Provider use it and exploit it.
Teams running Maven org.apache.dubbo:dubbo versions 2.5.0 to before 2.7.8 or com.alibaba:dubbo versions 2.5.0 to before 2.6.9 should check their deployments.