As of , CVE-2021-44228 in Apache Log4j2 is on CISA's list of exploited vulnerabilities: CISA listed it on . Our patch-first group: Patch this week.
CVE-2021-44228
Apache Log4j2: Remote Code Execution. Exploited, and in our Patch this week group.
Our patch-first group
Patch this week
- Ransomware use
- Metasploit module
- EPSS 0.99
CISA's 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.
Patch infofixed versions and vendor advice
What to install
Affects Apache Log4j2. The record gives its versions in a form this page does not read.
- EPSS score
- 0.99Higher than 99% of the CVEs EPSS scores.
EPSS estimates the chance of exploitation activity in the next 30 days.
- Exploited
- Yes CISA listed it on 10 December 2021
- US federal deadline
- 24 December 2021 14 days after CISA listed it. US federal civilian agencies must fix it by then.
- Used in ransomware campaigns
- Known
- EPSS when listed
- Not available CISA listed it before 4 February 2022, where the EPSS files we read begin.
- Public exploit
- 5 Metasploit modules and 3 Exploit-DB entries
In software packages
Affected packages
Software packages that the advisories for this CVE name. Each line is what one advisory says, with its id.
com.guicedee.services:log4j-coreMaven
Affects com.guicedee.services:log4j-core up to and including 1.2.1.2-jre17.
The advisory names no fixed version.
Advisory GHSA-jfh8-c2jp-5v3qorg.apache.logging.log4j:log4j-coreMaven
Affects org.apache.logging.log4j:log4j-core from 2.13.0 before 2.15.0, from 2.0-beta9 before 2.3.1 and from 2.4 before 2.12.2.
Fixed in 2.15.0, 2.3.1 and 2.12.2.
Advisory GHSA-jfh8-c2jp-5v3qorg.ops4j.pax.logging:pax-logging-log4j2Maven
Affects org.ops4j.pax.logging:pax-logging-log4j2 from 1.8.0 before 1.9.2, from 1.10.0 before 1.10.8, from 1.11.0 before 1.11.10 and from 2.0.0 before 2.0.11.
Fixed in 1.9.2, 1.10.8, 1.11.10 and 2.0.11.
Advisory GHSA-jfh8-c2jp-5v3qorg.xbib.elasticsearch:log4jMaven
Affects org.xbib.elasticsearch:log4j 6.3.2.1.
The advisory names no fixed version.
Advisory GHSA-jfh8-c2jp-5v3quk.co.nichesolutions.logging.log4j:log4j-coreMaven
Affects uk.co.nichesolutions.logging.log4j:log4j-core 2.6.3-CUSTOM.
The advisory names no fixed version.
Advisory GHSA-jfh8-c2jp-5v3q
Since listing
EPSS since listing
EPSS for CVE-2021-44228 since our EPSS history begins, on the days its value to 2 decimals changed. EPSS scores by FIRST.
Show the numbers
| From | EPSS |
|---|---|
| 0.94 | |
| 0.95 | |
| 0.90 | |
| 0.91 | |
| 0.95 | |
| 0.97 | |
| 0.98 | |
| 0.97 | |
| 0.98 | |
| 0.97 | |
| 0.96 | |
| 0.97 | |
| 0.94 | |
| 0.99 |
Timeline
What happened when
- The CVE record was published.
- CISA added it to its list of exploited vulnerabilities.
- Exploit-DB published an exploit (EDB-ID 50590).
- Exploit-DB published an exploit (EDB-ID 50592).
- The US federal deadline to fix it.
- Exploit-DB published an exploit (EDB-ID 51183).
CISA's required action
What CISA says to do
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.
Read further: CISA's catalog
The flaw
What the flaw is
Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
CISA's 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.
The CVE record's description, from apache
- CVE published
- 10 December 2021
- Assigned by
- apache
- CVSS
- 10.0 Critical (CVSS 3.1, from CISA-ADP)
- CWE-502
- Deserialization of Untrusted Data
- CWE-400
- Uncontrolled Resource Consumption
- CWE-20
- Improper Input Validation
- CISA SSVC, exploitation
- active
- CISA SSVC, automatable
- yes
- CISA SSVC, technical impact
- total
Public exploits
Public exploits
Facts from Metasploit's module list and Exploit-DB's index; we never copy exploit code.
Same product
Log4j2: other exploited entries
| Vulnerability | Product | Our group | Listed | Deadline | EPSS |
|---|---|---|---|---|---|
| CVE-2021-45046Deserialization of Untrusted Data | Log4j2 | Patch this weekRansomwareMetasploit | Due | 0.99 |
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- CWE names: Copyright © 2006-2026, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation (source). Licence: CWE Terms of Use
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)
- Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0