Remote code execution via unchecked RMI deserialization
Published Jul 29, 2021 · Updated Aug 4, 2024
Deserialization in Apache jUDDI before 3.3.10 allows remote attackers to execute arbitrary code by sending serialized objects to enabled RMI services. The RMI endpoints use Java default serialization and deserialize invocation parameters without validating incoming object data. RMI and JNDI registration are disabled by default, so exploitation requires an operator-enabled transport; successful exploitation runs code in the jUDDI process.
Summary
What happened
Deserialization in Apache jUDDI before 3.3.10 allows remote attackers to execute arbitrary code by sending serialized objects to enabled RMI services. The RMI endpoints use Java default serialization and deserialize invocation parameters without validating incoming object data. RMI and JNDI registration are disabled by default, so exploitation requires an operator-enabled transport; successful exploitation runs code in the jUDDI process.
The record
- CVE
- CVE-2021-37578
- Published
- Jul 29, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache jUDDI
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 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=unspecified <3.3.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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