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.
Remediation
References
https://lists.apache.org/thread.html/r99ef7fa35585d3a68762de07e8d2b2bc48b8fa669a03e8d84b9673f3%40%3Cdev.dubbo.apache.org%3E
Related Vulnerabilities
CVE-2021-21166 Vulnerability in maven package org.webjars.npm:electron
CVE-2020-2161 Vulnerability in maven package org.jenkins-ci.main:jenkins-core
CVE-2023-24438 Vulnerability in maven package org.jenkins-ci.plugins:jira-steps
CVE-2019-10410 Vulnerability in maven package org.jenkins-ci.plugins:log-parser
CVE-2020-2246 Vulnerability in maven package org.jenkins-ci.plugins:valgrind