CVE-2021-25641
Description
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.
How to fix
- apache dubbo2.6.9, 2.7.8 or later
- org.apache.dubbo:dubbo2.7.8 or later
- com.alibaba:dubbo2.6.9 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache dubbo | 2.5.0 ≤ v < 2.6.9, 2.7.0 ≤ v < 2.7.8 | 2.6.9, 2.7.8 |
| org.apache.dubbo:dubboMaven | 2.5.0 ≤ v < 2.7.8 | 2.7.8 |
| com.alibaba:dubboMaven | 2.5.0 ≤ v < 2.6.9 | 2.6.9 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.