CVE•Published 2022-01-18•Modified 2025-07-07•1 article on news•6 live references•NVD data

CVE-2022-23302Apache · Log4j

Vulnerability data via NVD (ingested)

CVSS v3.1

8.8

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS percentile

Exploit Prediction Scoring System · top 26% of all CVEs

Weaknesses (CWE)

CWE-502Deserialization of Untrusted Data

Description

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Timeline

Published 2022-01-18

Modified 2025-07-07

External references

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2022-23302

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Apache Log4j"

All exposed Apache Log4j instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Log4j"

HTTP body or banner mentions "Log4j" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2022-23302