Remote code execution via attacker-controlled JNDI lookup
Published Jan 18, 2022 · Updated May 27, 2026
Remote code execution in Apache Log4j 1.x allows remote authenticated users to execute code through a JMSSink JNDI lookup. JMSSink passes TopicConnectionFactoryBindingName to Context.lookup, allowing an attacker-controlled LDAP directory to return an unsafe object that JNDI instantiates. Exposure requires the non-default JMSSink component plus writable Log4j configuration or a referenced LDAP service accessible to the attacker.
Summary
What happened
Remote code execution in Apache Log4j 1.x allows remote authenticated users to execute code through a JMSSink JNDI lookup. JMSSink passes TopicConnectionFactoryBindingName to Context.lookup, allowing an attacker-controlled LDAP directory to return an unsafe object that JNDI instantiates. Exposure requires the non-default JMSSink component plus writable Log4j configuration or a referenced LDAP service accessible to the attacker.
The record
- CVE
- CVE-2022-23302
- Published
- Jan 18, 2022
- Updated
- May 27, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Log4j
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record 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=1.0.1 <unspecified
- Affected versionversion=unspecified <2.0-alpha1
What conditions does exploitation require?
What is affected?
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