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.
References
Link | Resource |
---|---|
https://lists.apache.org/thread.html/r99ef7fa35585d3a68762de07e8d2b2bc48b8fa669a03e8d84b9673f3%40%3Cdev.dubbo.apache.org%3E | Mailing List Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2021-05-29T07:30:12
Updated: 2021-05-29T07:30:12
Reserved: 2021-01-20T00:00:00
Link: CVE-2021-25641
JSON object: View
NVD Information
Status : Analyzed
Published: 2021-06-01T14:15:09.737
Modified: 2021-06-10T13:28:56.167
Link: CVE-2021-25641
JSON object: View
Redhat Information
No data.
CWE