Apache · Apache Log4j · CWE-20 · CWE-400 · CWE-502 · published 2021-12-10
CVE-2021-44228Apache Log4j2 Remote Code Execution Vulnerability
Patch today Known exploited and used in ransomware campaigns.
CVE-2021-44228 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2021-12-10, and it is known to be used in ransomware campaigns. EPSS estimates a 100% chance of exploitation in the next 30 days, higher than 100% of all CVEs. This Apache Log4j vulnerability: CVSS 10.0 (v3.1), attacks can be automated, a successful attack gives total control of the component. Patched packages are out for Debian and Ubuntu. US federal agencies must remediate by 2021-12-24. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
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. (federal due date 2021-12-24)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | apache-log4j1.2 | Not affected |
| 13 trixie | apache-log4j2 | Fixed in 2.15.0-1 | |
| 12 bookworm | apache-log4j1.2 | Not affected | |
| 12 bookworm | apache-log4j2 | Fixed in 2.15.0-1 | |
| Ubuntu | 20.04 LTS | apache-log4j2 | Fixed in 2.15.0-0.20.04.1 |
| 18.04 LTS | apache-log4j2 | Fixed in 2.10.0-2ubuntu0.1 | |
| Red Hat Enterprise Linux | RHEL 8 | log4j12 | Not affected |
| RHEL 7 | log4j | Not affected | |
| RHEL 6 | log4j | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
LibraryApache Log4j
Remote Code ExecutionCVE-2021-44228
Why: Known exploited and used in ransomware campaigns.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2021-12-10 | CISA KEV |
| Ransomware use | Known | CISA KEV |
| EPSS (30-day exploitation probability) | 100% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 10.0 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-20: Improper Input Validation · CWE-400: Uncontrolled Resource Consumption · CWE-502: Deserialization of Untrusted Data
More from this vendor: all Apache vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Apache Software Foundation Apache Log4j2
2.0-beta9to beforelog4j-core*(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.