Remote code execution via unchecked JNDI lookup
Published Jun 14, 2022 · Updated Aug 3, 2024
Deserialization in Apache Flume 1.4.0 through 1.9.0 allows remote attackers to execute code through a JMSSource JNDI LDAP URI. JMSSource passes its configured connectionFactory name to a JNDI lookup without validating the URI scheme, allowing an LDAP response to supply untrusted serialized data. Exploitation requires a JMS Source configured with the LDAP URI and attacker control of the referenced LDAP server.
Summary
What happened
Deserialization in Apache Flume 1.4.0 through 1.9.0 allows remote attackers to execute code through a JMSSource JNDI LDAP URI. JMSSource passes its configured connectionFactory name to a JNDI lookup without validating the URI scheme, allowing an LDAP response to supply untrusted serialized data. Exploitation requires a JMS Source configured with the LDAP URI and attacker control of the referenced LDAP server.
The record
- CVE
- CVE-2022-25167
- Published
- Jun 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Flume
- Classifications
- CWE-74, CWE-20
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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-jms-source <1.10.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