CVE-2022-34916 Improper Input Validation (JNDI Injection) in JMSMessageConsumer

Critical 9.8 Published Updated

Attackers can achieve remote code execution in Apache Flume if a JMS Source is configured with a malicious JNDI LDAP URI.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2022-34916?

CVE-2022-34916 is a critical code injection vulnerability in Apache Flume, published on 21 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Apache Flume versions 1.4.0 through 1.10.0 are vulnerable to a remote code execution (RCE) attack when a configuration uses a JMS Source with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI to allow only the use of the java protocol or no protocol.

Weakness: CWE-20

Which versions are affected by CVE-2022-34916?

2 open source packages ship an affected version, including org.apache.flume.flume-ng-sources:flume-jms-source. It affects 1 product.

PackageAffectedFixed in
org.apache.flume.flume-ng-sources:flume-jms-source MavenFrom 1.4.01.10.1
org.apache.flume.flume-ng-sources:flume-jms-source MavenFrom 1.4.01.10.1

Products include Apache Flume.

How do I fix CVE-2022-34916?

Upgrade org.apache.flume.flume-ng-sources:flume-jms-source to 1.10.1 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2022-34916 being exploited?

There is no known exploitation of CVE-2022-34916 in the wild and no public exploit code.

Sources

Also known as GHSA-h9mh-mgpv-gqmv.

Is CVE-2022-34916 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free