CVSS 3.1
10.0 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HKnown as Log4Shell
Critical (10.0) in Apache Log4j2. In CISA KEV since 2021-12-10, with known ransomware use. EPSS >99.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.logging.log4j:log4j-core 2.12.2, 2.15.0, 2.3.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Horg.apache.logging.log4j:log4j-core (Maven): fixed in 2.15.0, 2.3.1, 2.12.2org.ops4j.pax.logging:pax-logging-log4j2 (Maven): fixed in 1.9.2, 1.10.8, 1.11.10, 2.0.11Explain CVE-2021-44228 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-44228?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-44228?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-44228 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Log4j2 | from 2.0-beta9 before log4j-core* |
| Product | Fixed in |
|---|---|
| Apache Software Foundation Apache Log4j2 | 2.3.1 |
| Apache Software Foundation Apache Log4j2 | 2.12.2 |
| Apache Software Foundation Apache Log4j2 | 2.15.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jfh8-c2jp-5v3q | Maven | org.apache.logging.log4j:log4j-core | >=2.13.0 <2.15.0 | 2.15.0 |
| GHSA-jfh8-c2jp-5v3q | Maven | org.apache.logging.log4j:log4j-core | >=2.0-beta9 <2.3.1 | 2.3.1 |
| GHSA-jfh8-c2jp-5v3q | Maven | org.apache.logging.log4j:log4j-core | >=2.4 <2.12.2 | 2.12.2 |
| GHSA-jfh8-c2jp-5v3q | Maven | com.guicedee.services:log4j-core | <=1.2.1.2-jre17 | no fix published |
| GHSA-jfh8-c2jp-5v3q | Maven | org.xbib.elasticsearch:log4j | 6.3.2.1 | no fix published |
| GHSA-jfh8-c2jp-5v3q | Maven | uk.co.nichesolutions.logging.log4j:log4j-core | 2.6.3-CUSTOM | no fix published |
| GHSA-jfh8-c2jp-5v3q | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.8.0 <1.9.2 | 1.9.2 |
| GHSA-jfh8-c2jp-5v3q | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.10.0 <1.10.8 | 1.10.8 |
| GHSA-jfh8-c2jp-5v3q | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.11.0 <1.11.10 | 1.11.10 |
| GHSA-jfh8-c2jp-5v3q | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=2.0.0 <2.0.11 | 2.0.11 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 9 | apache-log4j2 | 2.7-2+deb9u1 | DLA-2842-1 |
| Debian | 10 | apache-log4j2 | 2.15.0-1~deb10u1 | DSA-5020-1 |
| Debian | 11 | apache-log4j2 | 2.15.0-1~deb11u1 | DSA-5020-1 |
| Debian | 12, 13, 14 | apache-log4j2 | 2.15.0-1 | DEBIAN-CVE-2021-44228 |
| Ubuntu | 18.04:LTS | apache-log4j2 | 2.10.0-2ubuntu0.1 | UBUNTU-CVE-2021-44228 USN-5192-1 |
| Ubuntu | 20.04:LTS | apache-log4j2 | 2.15.0-0.20.04.1 | UBUNTU-CVE-2021-44228 USN-5192-1 USN-5197-1 |
| Ubuntu | Pro:16.04:LTS | apache-log4j2 | 2.4-2ubuntu0.1~esm1 | UBUNTU-CVE-2021-44228 USN-5192-2 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-apache-cxf, eap7-apache-cxf-rt, eap7-apache-cxf-tools and 1 more | 0:3.1.16-4.redhat_00003.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-jackson-databind | 0:2.8.11.6-2.SP1_redhat_00002.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-jettison | 0:1.3.8-2.redhat_00002.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-netty, eap7-netty-all | 0:4.1.63-1.Final_redhat_00002.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-resteasy, eap7-resteasy-cdi, eap7-resteasy-jaxrs and 14 more | 0:3.0.27-1.Final_redhat_00001.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-snakeyaml | 0:1.33.0-1.SP1_redhat_00001.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-velocity | 0:1.7.0-3.redhat_00006.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.1::el7 | eap7-wildfly, eap7-wildfly-modules | 0:7.1.9-2.GA_redhat_00002.1.ep7.el7 | RHSA-2025:1746 |
| Red Hat | jboss_enterprise_application_platform_eus:7.3::el7 | eap7-hal-console | 0:3.2.17-1.Final_redhat_00001.1.el7eap | RHSA-2025:1747 |
| Red Hat | jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jackson-core, eap7-jackson-jaxrs-base, eap7-jackson-annotations and 5 more | 0:2.10.4-2.redhat_00004.1.el7eap | RHSA-2025:1747 |
| Red Hat | jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jackson-databind, eap7-jackson-modules-base, eap7-jackson-module-jaxb-annotations | 0:2.10.4-4.redhat_00004.1.el7eap | RHSA-2025:1747 |
| Red Hat | jboss_enterprise_application_platform_eus:7.3::el7 | eap7-jettison | 0:1.5.2-2.redhat_00002.1.el7eap | RHSA-2025:1747 |
| 4 more for Red Hat in the JSON and on Red Hat's page. | ||||
| SUSE | HPE Helion OpenStack 8, OpenStack Cloud 8 | venv-openstack-monasca | 2.2.2~dev1-11.32.1 | SUSE-SU-2021:4096-1 |
| SUSE | HPE Helion OpenStack 8, OpenStack Cloud 8, OpenStack Cloud Crowbar 8 | storm | 1.2.3-3.8.2 | SUSE-SU-2021:4096-1 |
| SUSE | OpenStack Cloud 9 | venv-openstack-monasca | 2.7.1~dev10-3.25.1 | SUSE-SU-2021:4097-1 |
| SUSE | OpenStack Cloud 9, OpenStack Cloud Crowbar 9 | storm | 1.2.3-3.5.1 | SUSE-SU-2021:4097-1 |
| openSUSE | Leap 15.2 | disruptor | 3.4.4-lp152.2.3.1 | openSUSE-SU-2021:1601-1 |
| openSUSE | Leap 15.2 | jakarta-servlet | 5.0.0-lp152.2.1 | openSUSE-SU-2021:1601-1 |
| openSUSE | Leap 15.2 | log4j | 2.13.0-lp152.3.3.1 | openSUSE-SU-2021:1577-1 |
| openSUSE | Leap 15.2 | log4j | 2.13.0-lp152.3.6.1 | openSUSE-SU-2021:1586-1 |
| openSUSE | Leap 15.2 | log4j | 2.16.0-lp152.3.9.1 | openSUSE-SU-2021:1601-1 |
| openSUSE | Leap 15.2 | logback | 1.2.8-lp152.2.3.2 | openSUSE-SU-2021:1613-1 |
| openSUSE | Leap 15.3 | disruptor | 3.4.4-3.3.1 | openSUSE-SU-2021:4107-1 |
| openSUSE | Leap 15.3 | jakarta-servlet | 5.0.0-5.3.1 | openSUSE-SU-2021:4107-1 |
| openSUSE | Leap 15.3 | log4j | 2.13.0-4.3.1 | openSUSE-SU-2021:3999-1 |
| openSUSE | Leap 15.3 | log4j | 2.13.0-4.6.1 | openSUSE-SU-2021:4094-1 |
| openSUSE | Leap 15.3 | log4j | 2.16.0-4.10.1 | openSUSE-SU-2021:4107-1 |
| openSUSE | Leap 15.3 | logback | 1.2.8-3.3.1 | openSUSE-SU-2021:4109-1 |
| 1 more for openSUSE in the JSON and on openSUSE's page. | ||||
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.
Red Hat rates this Critical.
This issue only affects log4j versions between 2.0 and 2.14.1. In order to exploit this flaw you need:
- A remotely accessible endpoint with any protocol (HTTP, TCP, etc) that allows an attacker to send arbitrary data,
- A log statement in the endpoint that logs the attacker controlled data.
In Red Hat OpenShift Logging the vulnerable log4j library is shipped in the Elasticsearch components. Because Elasticsearch is not susceptible to remote code execution with this vulnerability due to use of the Java Security Manager and because access to these components is limited, the impact by this vulnerability is reduced to Moderate.
As per upstream applications using Log4j 1.x may be impacted by this flaw if their configuration uses JNDI. However, the risk is much lower. This flaw in Log4j 1.x is tracked via https://access.redhat.com/security/cve/CVE-2021-4104 and has been rated as having Moderate security impact.
CodeReady Studio version 12.21.1 was released containing a fix for this vulnerability.
The following products are NOT affected by this flaw and have been explicitly listed here for the benefit of our customers.
- Red Hat Enterprise Linux
- Red Hat Advanced Cluster Management for Kubernetes
- Red Hat Advanced Cluster Security for Kubernetes
- Red Hat Ansible Automation Platform (Engine and Tower)
- Red Hat Certificate System
- Red Hat Directory Server
- Red Hat Identity Management
- Red Hat CloudForms
- Red Hat Update Infrastructure
- Red Hat Satellite
- Red Hat Ceph Storage
- Red Hat Gluster Storage
- Red Hat OpenShift Data Foundation
- Red Hat OpenStack Platform
- Red Hat Virtualization
- Red Hat Single Sign-On
- Red Hat 3scale API Management
For Log4j versions >=2.10
set the system property log4j2.formatMsgNoLookups or the environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS to true
For Log4j versions >=2.7 and <=2.14.1
all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m
For Log4j versions >=2.0-beta9 and <=2.10.0
remove the JndiLookup class from the classpath. For example:
```
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
```
On OpenShift 4 and in OpenShift Logging, the above mitigation can be applied by following the steps in this article: https://access.redhat.com/solutions/6578421
On OpenShift 3.11, mitigation to the affected Elasticsearch component can be applied by following the steps in this article: https://access.redhat.com/solutions/6578441
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift Logging 5.0 | openshift-logging/elasticsearch6-rhel8:v5.0.10-1 | Fixed 2021-12-14 | RHSA-2021:5137 |
| OpenShift Logging 5.1 | openshift-logging/elasticsearch6-rhel8:v6.8.1-67 | Fixed 2021-12-14 | RHSA-2021:5128 |
| OpenShift Logging 5.2 | openshift-logging/elasticsearch6-rhel8:v6.8.1-66 | Fixed 2021-12-14 | RHSA-2021:5127 |
| OpenShift Logging 5.3 | openshift-logging/elasticsearch6-rhel8:v6.8.1-65 | Fixed 2021-12-14 | RHSA-2021:5129 |
| Red Hat AMQ Streams 1.6.5 | Fixed 2021-12-14 | RHSA-2021:5133 | |
| Red Hat AMQ Streams 1.8.4 | log4j-core | Fixed 2021-12-14 | RHSA-2021:5138 |
| Red Hat Data Grid 8.2.2 | log4j-core | Fixed 2021-12-14 | RHSA-2021:5132 |
| Red Hat Fuse 7.10 | log4j-core | Fixed 2021-12-14 | RHSA-2021:5134 |
| Red Hat Fuse 7.8.2, 7.9.1, 7.10.1 | log4j-core | Fixed 2022-01-20 | RHSA-2022:0203 |
| Red Hat Integration | log4j-core | Fixed 2021-12-14 | RHSA-2021:5130 |
| A-MQ Clients 2 | log4j-core | Not affected | |
| Red Hat 3scale API Management Platform 2 | log4j | Not affected | |
| Red Hat AMQ Broker 7 | log4j | Not affected | |
| Red Hat build of Quarkus | log4j-core | Not affected | |
| Red Hat Decision Manager 7 | log4j-core | Not affected | |
| Red Hat Enterprise Linux 6 | log4j | Not affected | |
| Red Hat Enterprise Linux 7 | log4j | Not affected | |
| Red Hat Enterprise Linux 8 | parfait:0.5/log4j12 | Not affected | |
| Red Hat Integration Camel Quarkus 1 | log4j-core | Affected | |
| Red Hat JBoss Enterprise Application Platform 6 | log4j | Not affected | |
| 43 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2021-44228.
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-22-034-01 | Sensormatic PowerManage (Update A) | 2022-02-03 | Critical Manufacturing | PowerManage: Versions 4.0 to 4.8 | none listed |
| ICSA-21-357-02 | Johnson Controls exacq Enterprise Manager | 2021-12-23 | Critical Manufacturing | Exacq Enterprise Manager: All Versions 21.12 and prior | none listed |
From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).