Skip to main content
ExploitedIn CISA KEVFix available

CVE-2021-44228

Log4Shell

Exploitation confirmed. First attested on 2021-12-10 by CISA-ADP, CISA KEV, GCVE · kevintel, GCVE · shadowserver.

  • Published2021-12-10
  • Fixed in2.15.0 · 2.12.2 · 2.3.1
  • TwinCVE-2021-45046
  • WeaknessCWE-20 · CWE-400 · CWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2021-12-10Added to the CISA KEV catalogCISA KEV
  2. 2021-12-10Listed as exploited by GCVEGCVE
  3. 2021-12-10Exploitation first reportedCISA KEV
  4. 2021-12-1010:15CVE publishedNVD
  5. 2021-12-14Exploit-DB entryExploit-DB
  6. 2025-02-0414:25SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-11-03 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-44228?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-44228?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Apache Log4j
BranchAffectedFixed in
2.x≥ 2.13.0, < 2.15.02.15.0
2.x≥ 2.4.0, < 2.12.22.12.2
2.x≥ 2.4, < 2.12.22.12.2
2.x≥ 2.0.1, < 2.3.12.3.1
2.x≥ 2.0-beta9, < 2.3.12.3.1
2.0= 2.0no fix published
Cisco sd-wan vmanage
BranchAffectedFixed in
20.6≥ 20.6, < 20.6.2.120.6.2.1
20.5≥ 20.5, < 20.5.1.120.5.1.1
20.4≥ 20.4, < 20.4.2.120.4.2.1
20.3< 20.3.4.120.3.4.1
20.3= 20.3no fix published
20.4= 20.4no fix published
20.5= 20.5no fix published
20.6= 20.6no fix published
20.6= 20.6.1no fix published
20.7= 20.7no fix published
20.8= 20.8no fix published
Cisco ucs central software
BranchAffectedFixed in
2.0= 2.0no fix published
2.0= 2.0\(1a\)no fix published
2.0= 2.0\(1b\)no fix published
2.0= 2.0\(1c\)no fix published
2.0= 2.0\(1d\)no fix published
2.0= 2.0\(1e\)no fix published
2.0= 2.0\(1f\)no fix published
2.0= 2.0\(1g\)no fix published
2.0= 2.0\(1h\)no fix published
2.0= 2.0\(1k\)no fix published
2.0= 2.0\(1l\)no fix published

144 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Log4j2
    Affected
    • ≥ 2.0-beta9, < log4j-core*fixed in log4j-core*custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-04-03

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-log4j2Ubuntu:Pro:16.04:LTSall versions · fixed in 2.4-2ubuntu0.1~esm1
  • apache-log4j2Ubuntu:20.04:LTSall versions · fixed in 2.15.0-0.20.04.1
  • apache-log4j2Ubuntu:20.04:LTSall versions · fixed in 2.16.0-0.20.04.1
  • apache-log4j2Ubuntu:18.04:LTSall versions · fixed in 2.10.0-2ubuntu0.1
  • apache-log4j2Debian:14all versions · fixed in 2.15.0-1
  • apache-log4j2Debian:13all versions · fixed in 2.15.0-1
  • apache-log4j2Debian:12all versions · fixed in 2.15.0-1
  • apache-log4j2Debian:11all versions · fixed in 2.15.0-1~deb11u1

48 more package ranges on OSV.dev

Vendor advisories

  • CVE-2021-44228 Red Hat Product Security122 products fixed · 4 known affected

    log4j-core: Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value

    log4j-core as a component of Red Hat Integration Camel Quarkus 1 · log4j-core as a component of Red Hat JBoss Enterprise Application Platform 7 · opendaylight as a component of Red Hat OpenStack Platform 13 (Queens) · +1 more

  • RHSA-2025:1747 Red Hat Product Security52 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.12 security update

  • RHSA-2025:1746 Red Hat Product Security37 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.9 on RHEL 7 security update

  • ICSA-22-034-01 CISA1 known affected

    Sensormatic PowerManage (Update A)

    PowerManage: Versions 4.0 to 4.8

  • RHSA-2022:0296 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Process Automation Manager 7.12.0 security update

  • RHSA-2022:0203 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Fuse 7.8-7.10 security update

24 more advisories

Full record on NVD

Fix

  1. Update Apache Log4j to 2.15.0 · 2.12.2 · 2.3.1
  2. CISA’s 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.due 2021-12-24
  3. Vendor fix Red Hat Product Security RHSA-2025:1747 · 52 productsBefore applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access…
  4. Vendor fix Red Hat Product Security RHSA-2025:1746 · 37 productsBefore applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access…
  5. Vendor fix CISA ICSA-22-034-01 · 1 productUpgrade PowerManage to Version 4.10
  6. Vendor fix Red Hat Product Security RHSA-2022:0296 · 1 productFor on-premise installations, before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. It is recommended to halt the server by stopping the JBoss Application Server process before installing this up…
  7. Vendor fix Red Hat Product Security RHSA-2022:0203 · 1 productBefore applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. Installation instructions are available from the Fuse product documentation pages: Fuse 7.8: https://access.redhat.com/documentation/en-us/r…
  8. Vendor fix Siemens ProductCERT SSA-479842 · 5 productsVulnerabilities fixed on central cloud service between 2021-12-10 (CVE-2021-44228) and 2021-12-21 (CVE-2021-45105); no user actions necessary

Advisories and patches

Detection

read 2026-11-02 22:42 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
EDB-50590EDB-50592EDB-51183
Exploit-DB
Proof-of-concept repositories
20 repositories, unverifiedtangxiaofeng7/CVE-2021-44228-Apache-Log4j-RceGlease/Healerjacobtread/L4J-Vuln-Patchjas502n/Log4j2-CVE-2021-44228HyCraftHD/Log4J-RCE-Proof-Of-Concept
PoC-in-GitHub
Metasploit modules
5 modulesexploit/linux/http/mobileiron_core_log4shellrank: excellentexploit/multi/http/log4shell_header_injectionrank: excellentexploit/multi/http/ubiquiti_unifi_log4shellrank: excellentModule metadata: Metasploit Framework, © Rapid7, Inc., BSD-3-Clause.
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2021-12-10
Patch Due Date
2021-12-24
Ransomware Use
Known
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.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Published
2021-12-10
Last Modified
2026-08-11
NVD status
Analyzed
GitHub Advisory
GHSA-jfh8-c2jp-5v3q

Frequently asked questions

What is CVE-2021-44228?

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.

Is CVE-2021-44228 actively exploited?

Yes. CVE-2021-44228 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2021-12-24.

What is the CVSS score for CVE-2021-44228?

CVE-2021-44228 has a CVSS v3 base score of 10 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Running Apache Log4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, December 2021Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record