Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

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.

Exploited in the wild

CISA lists this vulnerability in its Known Exploited Vulnerabilities catalog as Apache Log4j2 Remote Code Execution Vulnerability.

Added
10 Dec 2021
Fix due (US federal)
24 Dec 2021
Used by ransomware
Known

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.

ENISA's EU Vulnerability Database lists it as exploited, from CISA's KEV, since 10 Dec 2021.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. The public collections list 5 Metasploit modules, a Nuclei template and 3 Exploit-DB entries for it. CISA's SSVC rates its exploitation: it is being exploited.

Show the exploits9

Metasploit modules5 modules

Nuclei templates1 template

Exploit-DB3 entries

Modules, templates and exploits as listed by the Metasploit Framework (BSD-3-Clause), ProjectDiscovery's Nuclei templates (MIT) and the Exploit Database (GPLv2), read once a day. Where the data comes from

Timeline

  1. ID reserved

    By apache

  2. · 14 days later

    Published

  3. Added to CISA KEV

    Known exploited, also by ransomware

  4. · 4 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-44228, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Critical10.0CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical10.0CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
100.0% · top 0.1% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: active · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 10.0.

Affected products

Affected packages

Affected packages5

From reviewed advisories of the GitHub Advisory Database.

References

References52

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-44228 badge
[![CVE-2021-44228](https://cveledger.app/badge/CVE-2021-44228.svg)](https://cveledger.app/cve/CVE-2021-44228)

Record last updated .