OR
     *cpe:2.3:a:apache:juddi:*:*:*:*:*:*:*:* versions up to (excluding) 3.3.10

NIST (AV:N/AC:M/Au:N/C:P/I:P/A:P)

NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

NIST CWE-502

http://www.openwall.com/lists/oss-security/2021/07/29/1 No Types Assigned

http://www.openwall.com/lists/oss-security/2021/07/29/1 Mailing List, Third Party Advisory

https://lists.apache.org/thread.html/r82047b3ba774cf870ea8e1e9ec51c6107f6cd056d4e36608148c6e71%40%3Cprivate.juddi.apache.org%3E No Types Assigned

https://lists.apache.org/thread.html/r82047b3ba774cf870ea8e1e9ec51c6107f6cd056d4e36608148c6e71%40%3Cprivate.juddi.apache.org%3E Broken Link, Mailing List, Third Party Advisory

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

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 jU

http://www.openwall.com/lists/oss-security/2021/07/29/1 [No Types Assigned]