CVE-2021-25641

Dubbo Zookeeper does not check serialization id

Published May 29, 2021 CVSS 3.1 · 9.8 Critical EPSS 21.2% KEV · Not listed
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

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-v2rg-8cwr-75g8 Deserializer tampering in Apache Dubbo
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 3, 2024, 8:11 PM
Reserved
Jan 20, 2021, 12:00 AM
Status
Modified
Published
Jun 1, 2021, 2:15 PM
Modified
Jun 17, 2026, 3:42 AM