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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v2rg-8cwr-75g8 | Deserializer tampering in Apache Dubbo |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2024-08-03T20:11:27.972Z
Reserved: 2021-01-20T00:00:00
Link: CVE-2021-25641
No data.
Status : Modified
Published: 2021-06-01T14:15:09.737
Modified: 2024-11-21T05:55:11.660
Link: CVE-2021-25641
No data.
OpenCVE Enrichment
No data.
Github GHSA