CVSS 3.1
6.6 mediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HMedium (6.6). EPSS 98% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.logging.log4j:log4j-core 2.12.4, 2.17.1, 2.3.2.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:Horg.apache.logging.log4j:log4j-core (Maven): fixed in 2.3.2, 2.12.4, 2.17.1org.ops4j.pax.logging:pax-logging-log4j2 (Maven): fixed in 1.9.2, 1.10.9, 1.11.13, 2.0.14Explain CVE-2021-44832 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-44832?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-44832?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-44832 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 log4j-core before 2.17.1 |
| Product | Fixed in |
|---|---|
| Apache Software Foundation Apache Log4j2 | 2.12.4 |
| Apache Software Foundation Apache Log4j2 | 2.3.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-8489-44mv-ggj8 | Maven | org.apache.logging.log4j:log4j-core | >=2.0-beta7 <2.3.2 | 2.3.2 |
| GHSA-8489-44mv-ggj8 | Maven | org.apache.logging.log4j:log4j-core | >=2.4 <2.12.4 | 2.12.4 |
| GHSA-8489-44mv-ggj8 | Maven | org.apache.logging.log4j:log4j-core | >=2.13.0 <2.17.1 | 2.17.1 |
| GHSA-8489-44mv-ggj8 | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.8.0 <1.9.2 | 1.9.2 |
| GHSA-8489-44mv-ggj8 | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.10.0 <1.10.9 | 1.10.9 |
| GHSA-8489-44mv-ggj8 | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=1.11.0 <1.11.13 | 1.11.13 |
| GHSA-8489-44mv-ggj8 | Maven | org.ops4j.pax.logging:pax-logging-log4j2 | >=2.0.0 <2.0.14 | 2.0.14 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 9 | apache-log4j2 | 2.12.4-0+deb9u1 | DLA-2870-1 |
| Debian | 12, 13, 14 | apache-log4j2 | 2.17.1-1 | DEBIAN-CVE-2021-44832 |
| Ubuntu | 18.04:LTS | apache-log4j2 | 2.12.4-0ubuntu0.1 | UBUNTU-CVE-2021-44832 USN-5222-1 |
| Ubuntu | 20.04:LTS | apache-log4j2 | 2.17.1-0.20.04.1 | UBUNTU-CVE-2021-44832 USN-5222-1 |
| Ubuntu | 25.10, 26.10, Pro:16.04:LTS | apache-log4j2 | no fix listed | UBUNTU-CVE-2021-44832 |
| Red Hat | jboss_enterprise_application_platform:7.4::el7 | eap7-log4j | 0:2.17.1-1.redhat_00001.1.el7eap | RHSA-2022:1296 |
| Red Hat | jboss_enterprise_application_platform:7.4::el8 | eap7-log4j | 0:2.17.1-1.redhat_00001.1.el8eap | RHSA-2022:1297 |
| openSUSE | Leap 15.2 | log4j | 2.17.0-lp152.3.15.1 | openSUSE-SU-2022:0002-1 |
| openSUSE | Leap 15.3 | log4j | 2.17.0-4.16.1 | openSUSE-SU-2021:4208-1 |
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 · openSUSE.
Red Hat rates this Moderate.
Log4j 1.x is not impacted by this vulnerability. Therefore versions of log4j shipped with Red Hat Enterprise Linux are NOT affected by this flaw.
For Elasticsearch, as shipped in OpenShift Container Platform and OpenShift Logging, access to the log4j2.properties configuration is limited only to the cluster administrators and exploitation requires cluster logging changes, what reduced the impact of this vulnerability significantly [0].
[0] https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476#update-jan-6-5
As per upstream:
- In prior releases confirm that if the JDBC Appender is being used it is not configured to use any protocol other than Java.
- Note that only the log4j-core JAR file is impacted by this vulnerability. Applications using only the log4j-api JAR file without the log4j-core JAR file are not impacted by this vulnerability.
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift Logging 5.0 | openshift-logging/elasticsearch6-rhel8:v5.0.12-1 | Fixed 2022-01-20 | RHSA-2022:0225 |
| OpenShift Logging 5.1 | openshift-logging/elasticsearch6-rhel8:v6.8.1-98 | Fixed 2022-01-20 | RHSA-2022:0226 |
| OpenShift Logging 5.2 | openshift-logging/elasticsearch6-rhel8:v6.8.1-100 | Fixed 2022-01-21 | RHSA-2022:0230 |
| OpenShift Logging 5.3 | openshift-logging/elasticsearch6-rhel8:v6.8.1-99 | Fixed 2022-01-20 | RHSA-2022:0227 |
| Red Hat AMQ Streams 1.6.7 | Fixed 2022-02-08 | RHSA-2022:0467 | |
| Red Hat AMQ Streams 2.0.0 | log4j-core | Fixed 2022-01-13 | RHSA-2022:0138 |
| Red Hat Data Grid 8.2.3 | log4j-core | Fixed 2022-01-20 | RHSA-2022:0205 |
| Red Hat Fuse 7.8.2, 7.9.1, 7.10.1 | log4j-core | Fixed 2022-01-20 | RHSA-2022:0203 |
| Red Hat Integration Camel Extensions for Quarkus 2.2 | Fixed 2022-01-20 | RHSA-2022:0222 | |
| Red Hat Integration Camel-K 1.6.3 | log4j-core | Fixed 2022-01-20 | RHSA-2022:0223 |
| A-MQ Clients 2 | log4j-core | Not affected | |
| Red Hat AMQ Broker 7 | log4j-core | 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 | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | log4j-core | Not affected | |
| 18 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-44832.
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-74 (37), CWE-20 (51).