SECUFOCUSNOW
Home›CVE index›CVE-2021-44228
CISA KEV · Known exploitedCritical

CVE-2021-44228

Apache Log4j2

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 vuln...

CVSS
10
EPSS
100.0%
100.0% percentile
CISA KEV
Listed
Published
2021.12.10
PRIORITY ASSESSMENT

Immediate review

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog.

Known exploitationConfirmed by CISA KEV
Exploit probability100.0%
Technical severityCVSS 10

Vulnerability overview

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 vuln...

Affected product and versions

Product
Apache Log4j2
Affected versions
2.0-beta9, < 2.7.0, >= 2.0.1 < 2.3.1, >= 2.4.0 < 2.12.2, >= 2.13.0 < 2.15.0, 2.0, < 2019.1, 2019.1, < 10.4.2, 3.0, 4.0, 4.1, 4.2, 5.0, 5.1, < 2021-12-13, 3.1, 8.5, 8.6, 8.7
Fixed versions
2.7.0, 2.3.1, 2.12.2, 2.15.0, 2019.1, 10.4.2, 2021-12-13, 3.8.0.12, 8.6.2j-398, 2021-12-16, 3.5, 4.4.1, 2020, 4.70, 2.30, 5.1, 10.0.13, 3.5.4, 2.1.0, 2021.11_1.162

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
CISA required action

For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

Due date: 2021.12.24
  1. 1
    Identify

    Confirm that Apache Log4j2 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE
CWE-20, CWE-400, CWE-502, CWE-917
KEV added
2021.12.10
Ransomware use
확인됨