CVE•Published 2021-12-10•1 article on news•6 live references•NVD data

CVE-2021-44228

Vulnerability data via CVEDB (Shodan)

CVSS v3.1

10.0

CRITICAL

EPSS percentile

100

Exploit Prediction Scoring System · top 0% of all CVEs

Description

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Timeline

Published 2021-12-10

External references

NVD MITRE Exploit-DB Sploitus 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 tag4 hosts

vuln:CVE-2021-44228

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product + version

product:"Apache Log4j" version:"2.0"

Version-pinned fingerprint from NVD's first vulnerable CPE.

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-2021-44228