oss-security - CVE-2022-25167 - Apache Flume JMSSource does not protect from malicious JNDI urls

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <EC5BDCA4-8FF7-41E0-9177-5F4DD8A96841@apache.org>
Date: Tue, 14 Jun 2022 00:22:00 -0700
From: Ralph Goers <rgoers@...che.org>
To: announce@...che.org
Cc: oss-security@...ts.openwall.com
Subject: CVE-2022-25167 - Apache Flume JMSSource does not protect from
 malicious JNDI urls

Severity, medium

Description:

Flume’s JMSSource class can be configured with a connection factory name. A JNDI lookup is performed on this name without performing an validation. This could result in untrusted data being deserialized.

Mitigation
Upgrade to Flume 1.10.0.

In releases 1.4.0 through 1.9.0 the JMSSource should not be used.

Release Details
In release 1.10.0, if a protocol is specified in the connection factory parameter only the java protocol will be allowed. If no protocol is specified it will also be allowed.

Credit
This issue was found by the Flume development team.

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.