Remote code execution via unsafe JNDI provider URL
Published Oct 26, 2022 · Updated May 7, 2025
JNDI injection in Apache Flume 1.4.0 through 1.10.1 allows remote attackers to execute code through an unsafe JMS Source providerURL. JMSSource passes the configured providerUrl to a JNDI InitialContext lookup without validating the name, allowing deserialization of data from an untrusted provider. Exploitation requires a JMS Source configured with an unsafe providerURL; successful code runs in the Flume agent process.
Summary
What happened
JNDI injection in Apache Flume 1.4.0 through 1.10.1 allows remote attackers to execute code through an unsafe JMS Source providerURL. JMSSource passes the configured providerUrl to a JNDI InitialContext lookup without validating the name, allowing deserialization of data from an untrusted provider. Exploitation requires a JMS Source configured with an unsafe providerURL; successful code runs in the Flume agent process.
The record
- CVE
- CVE-2022-42468
- Published
- Oct 26, 2022
- Updated
- May 7, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Flume
- Classifications
- CWE-74, CWE-20
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Flume JMSSource <1.11.0 changes=[{"at":"1.4.0","status":"affected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo