Deserialization in Apache Juddi
CVE-2021-37578
Apache jUDDI uses several classes related to Java's Remote Method Invocation (RMI) which (as an extension to UDDI) provides an alternate transport for accessing UDDI services. RMI uses the default Java serialization mechanism to pass parameters in RMI invocations. A remote attacker can send a malicious serialized object to the above RMI entries. The objects get deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely. For both jUDDI web service applications and jUDDI clients, the usage of RMI is disabled by default. Since this is an optional feature and an extension to the UDDI protocol, the likelihood of impact is low. Starting with 3.3.10, all RMI related code was removed.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.041, 90.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Apache Juddi
- Apache Software Foundation Juddi — versions unspecified
Weakness classification (CWE)
References
- lists.apache.org/thread.html/r82047b3ba774cf870ea8e1e9ec51c6107f6cd056d4e366081… (Mailing List, Third Party Advisory, Broken Link)
- [oss-security] 20210728 [SECURITY] CVE-2021-37578 Apache jUDDI Remote code execution (mailing-list, Mailing List, Third Party Advisory)