Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 28 Jul 2021 18:35:17 -0400
From: "Alex O'Ree" <>
To: "" <>,, 
	security <>,, 
	Artem Smotrakov <>
Subject: [SECURITY] CVE-2021-37578 Apache jUDDI Remote code execution

CVE-2021-37578 Apache jUDDI Remote code execution

Severity: Low

VERSION:  older than 3.3.10

PROBLEMTYPE: Remote Code Execution


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.


jUDDI Clients, disable RMITransports (found in uddi.xml) and use alternate
transports such as HTTPS.
jUDDI Server (juddiv3.war/WEB-INF/classes/juddiv3.xml), disable JNDI and
RMI settings in juddiv3.xml.
The appropriate settings are located below in xpath style notation.


If the settings are not present, then JNDI and RMI are already disabled.
This is the default setting.

Reported by Artem Smotrakov

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.