Unauthenticated code execution via unsafe bean stringification
Published Sep 9, 2021 · Updated Aug 4, 2024
Remote code execution in Apache Dubbo 2.7.0 through 2.7.12 allows remote attackers to execute code via crafted RPC arguments. Timeout, cache, and other diagnostic paths stringify deserialized RPC argument objects, invoking an attacker-controlled bean's toString method. No authentication or user interaction is required; successful exploitation runs code in the Dubbo service process.
Summary
What happened
Remote code execution in Apache Dubbo 2.7.0 through 2.7.12 allows remote attackers to execute code via crafted RPC arguments. Timeout, cache, and other diagnostic paths stringify deserialized RPC argument objects, invoking an attacker-controlled bean's toString method. No authentication or user interaction is required; successful exploitation runs code in the Dubbo service process.
The record
- CVE
- CVE-2021-36161
- Published
- Sep 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Dubbo
- Classifications
- CWE-134, CAPEC-135, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Dubbo 2.7.x <=2.7.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo