cve.bz

CVE-2021-44832 Injection

6.6 mediumEPSS 98%Fix available

Medium (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.

On this page
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
98% (unchanged from 98% a week ago; 98% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Log4j2from log4j-core before 2.17.1

Fixed in

ProductFixed in
Apache Software Foundation Apache Log4j22.12.4
Apache Software Foundation Apache Log4j22.3.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8489-44mv-ggj8Mavenorg.apache.logging.log4j:log4j-core>=2.0-beta7 <2.3.22.3.2
GHSA-8489-44mv-ggj8Mavenorg.apache.logging.log4j:log4j-core>=2.4 <2.12.42.12.4
GHSA-8489-44mv-ggj8Mavenorg.apache.logging.log4j:log4j-core>=2.13.0 <2.17.12.17.1
GHSA-8489-44mv-ggj8Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.8.0 <1.9.21.9.2
GHSA-8489-44mv-ggj8Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.10.0 <1.10.91.10.9
GHSA-8489-44mv-ggj8Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.11.0 <1.11.131.11.13
GHSA-8489-44mv-ggj8Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=2.0.0 <2.0.142.0.14

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian9apache-log4j22.12.4-0+deb9u1DLA-2870-1
Debian12, 13, 14apache-log4j22.17.1-1DEBIAN-CVE-2021-44832
Ubuntu18.04:LTSapache-log4j22.12.4-0ubuntu0.1UBUNTU-CVE-2021-44832 USN-5222-1
Ubuntu20.04:LTSapache-log4j22.17.1-0.20.04.1UBUNTU-CVE-2021-44832 USN-5222-1
Ubuntu25.10, 26.10, Pro:16.04:LTSapache-log4j2no fix listedUBUNTU-CVE-2021-44832
Red Hatjboss_enterprise_application_platform:7.4::el7eap7-log4j0:2.17.1-1.redhat_00001.1.el7eapRHSA-2022:1296
Red Hatjboss_enterprise_application_platform:7.4::el8eap7-log4j0:2.17.1-1.redhat_00001.1.el8eapRHSA-2022:1297
openSUSELeap 15.2log4j2.17.0-lp152.3.15.1openSUSE-SU-2022:0002-1
openSUSELeap 15.3log4j2.17.0-4.16.1openSUSE-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

Red Hat rates this Moderate.

Red Hat's statement

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

Red Hat's mitigation

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.

ProductPackageStateAdvisory
OpenShift Logging 5.0openshift-logging/elasticsearch6-rhel8:v5.0.12-1Fixed 2022-01-20RHSA-2022:0225
OpenShift Logging 5.1openshift-logging/elasticsearch6-rhel8:v6.8.1-98Fixed 2022-01-20RHSA-2022:0226
OpenShift Logging 5.2openshift-logging/elasticsearch6-rhel8:v6.8.1-100Fixed 2022-01-21RHSA-2022:0230
OpenShift Logging 5.3openshift-logging/elasticsearch6-rhel8:v6.8.1-99Fixed 2022-01-20RHSA-2022:0227
Red Hat AMQ Streams 1.6.7Fixed 2022-02-08RHSA-2022:0467
Red Hat AMQ Streams 2.0.0log4j-coreFixed 2022-01-13RHSA-2022:0138
Red Hat Data Grid 8.2.3log4j-coreFixed 2022-01-20RHSA-2022:0205
Red Hat Fuse 7.8.2, 7.9.1, 7.10.1log4j-coreFixed 2022-01-20RHSA-2022:0203
Red Hat Integration Camel Extensions for Quarkus 2.2Fixed 2022-01-20RHSA-2022:0222
Red Hat Integration Camel-K 1.6.3log4j-coreFixed 2022-01-20RHSA-2022:0223
A-MQ Clients 2log4j-coreNot affected
Red Hat AMQ Broker 7log4j-coreNot affected
Red Hat build of Quarkuslog4j-coreNot affected
Red Hat Decision Manager 7log4j-coreNot affected
Red Hat Enterprise Linux 6log4jNot affected
Red Hat Enterprise Linux 7log4jNot affected
Red Hat Enterprise Linux 8parfait:0.5/log4j12Not affected
Red Hat Integration Camel Quarkus 1log4j-coreAffected
Red Hat JBoss Enterprise Application Platform 6log4jNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packlog4j-coreNot 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.

Detection rules

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.

Attack patterns (CAPEC)

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

References

Check your stackJSON