CVE-2021-25641: Dubbo Zookeeper does not check serialization id
Apache Software Foundation · Apache Dubbo
Fixed in 2.7.8 · Affected: Apache Software Foundation Apache Dubbo before 2.7.8 · Exploitation: likely to be exploited (10% or more)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 97% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Apache Software Foundation · Apache Dubbofrom Apache Dubbo 2.7.x before 2.7.8; from Apache Dubbo 2.6.x before 2.6.9
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- May 2021
CoverageNo articles yet
No CyberSIXT article names CVE-2021-25641 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.