CVE-2021-44832
MediumExploitedImproper Input Validation and Injection in Apache Log4j2
Published Jan 4, 2022 · Updated Aug 4, 2026 · Also known as DEBIAN-CVE-2021-44832, DLA-2870-1, GHSA-8489-44mv-ggj8, ROOT-APP-MAVEN-CVE-2021-44832, TR-21-1035, TR-21-1038, UBUNTU-CVE-2021-44832, USN-5222-1
Key Facts
Patch immediately- CVE-2021-44832 is a medium-severity vulnerability (CVSS 6.6 v3.1) affecting Log4j (Apache), Cloudcenter (Cisco), Communications Brm - Elastic Charging Engine (Oracle) and 22 more products.
- It is exploited in the wild, listed in Industry KEV feed since Feb 14, 2023 and is known to be used in ransomware campaigns. No public exploit code is known.
- EPSS estimates a 98% probability of exploitation in the next 30 days.
- Fixed versions are available, including Log4j 2.3.2, Log4j 2.17.0-4.16.1, Log4j 2.17.0-lp152.3.15.1.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
6.6
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
98%
Higher than 99.9% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing, used by ransomware
Public exploit code
None known
Get the full CVE-2021-44832 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Feb 14, 2023 | n/a | Known |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
99 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Log4jApache | 2.0, 2.0-beta7, 2.0-beta8, 2.0-beta9, 2.0-rc1, 2.0-rc2 | 2.3.2 |
| CloudcenterCisco | 4.10.0.16 | n/a |
| Communications Brm - Elastic Charging EngineOracle | 12.0.0.5.0 | 12.0.0.4.6 |
| Communications Diameter Signaling RouterOracle | See advisory | 8.5.1.0 |
| Communications Interactive Session RecorderOracle | 6.3, 6.4 | n/a |
Patched Releases
Log4j
2.3.2, 2.17.0-4.16.1, 2.17.0-lp152.3.15.1, 2.17.1-1.1, 2.17.1-1.amzn2022.0.1, 2.17.2-1.amzn2022.0.3
Apache Log4j2
2.17.1, 2.12.4-0+deb9u1, 2.12.4-0ubuntu0.1, 2.17.1-0.20.04.1, 2.17.1-1, 2.17.1-1~deb11u1
aws-kinesis-agent
2.0.6-1.amzn2
eap7-log4j
0:2.17.1-1.redhat_00001.1.el7eap, 0:2.17.1-1.redhat_00001.1.el8eap
io.root.org.apache.logging.log4j:log4j-core
2.12.4-root.io.1, 2.12.4-root.io.10, 2.12.4-root.io.2, 2.12.4-root.io.3, 2.12.4-root.io.9, 2.17.0-root.io.11, 2.17.0-root.io.12
log4j-javadoc
2.17.0-4.16.1, 2.17.0-lp152.3.15.1, 2.17.1-1.1
log4j-jcl
2.17.0-4.16.1, 2.17.0-lp152.3.15.1, 2.17.1-1.1, 2.17.1-1.amzn2022.0.1, 2.17.2-1.amzn2022.0.3
log4j-slf4j
2.17.0-4.16.1, 2.17.0-lp152.3.15.1, 2.17.1-1.1, 2.17.1-1.amzn2022.0.1, 2.17.2-1.amzn2022.0.3
openshift-logging/elasticsearch6-rhel8:v5.0.12
1
openshift-logging/elasticsearch6-rhel8:v6.8.1
98
openshift3/ose-logging-elasticsearch5:v3.11.570
2.ge84e80c
openshift4/ose-logging-elasticsearch6:v4.6.0
202201181437.p0.g181b827.assembly.stream
openshift4/ose-metering-hive:v4.7.0
202201271626.p0.g12e974d.assembly.stream
openshift4/ose-metering-hive:v4.8.0
202201271626.p0.g8fb24af.assembly.stream
openshift4/ose-metering-presto:v4.7.0
202201271626.p0.g2155d34.assembly.stream
openshift4/ose-metering-presto:v4.8.0
202201271626.p0.gf1abc62.assembly.stream
Communications Brm - Elastic Charging Engine
12.0.0.4.6
Communications Diameter Signaling Router
<=8.5.1.0
Communications Offline Mediation Controller
12.0.0.4.4
Policy Automation
<=12.2.24
Policy Automation For Mobile Devices
<=12.2.24
Primavera Gateway
<=17.12.11
Primavera P6 Enterprise Project Portfolio Management
<=19.12.18.0
Siebel Ui Framework
<=21.12
org.apache.logging.log4j:log4j-core
2.12.4, 2.12.4-aikido.10, 2.14.1+sp2, 2.17.1, 2.3.2
Timeline
Publicly disclosed
Jan 4, 2022
Added to Industry KEV feed
Feb 14, 2023
Last updated
Aug 4, 2026
Weakness Type
- CWE-20 Improper Input Validation
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
References
- advisoryhttp://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22096
- advisoryhttp://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35493
- advisoryhttp://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35550
- advisoryhttp://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35662
- advisoryhttp://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36090
FAQ
Common Questions.
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.
Affected: Log4j (Apache) versions 2.0, 2.0-beta7, 2.0-beta8, 2.0-beta9, 2.0-rc1, 2.0-rc2; Cloudcenter (Cisco) versions 4.10.0.16; Communications Brm - Elastic Charging Engine (Oracle) versions 12.0.0.5.0, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since Feb 14, 2023 and is known to be used in ransomware campaigns.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Log4j 2.3.2, Log4j 2.17.0-4.16.1, Log4j 2.17.0-lp152.3.15.1.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2021-44832 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo