Skip to content
Noroxi
CVE-2021-44228· NVD / CVE Program· CNA apache

Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

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.

CriticalCVSS 10.0 · v3.1KEVWeaponized Fix available
Published
Dec 10, 2021
Updated
Aug 11, 2026
EPSS
100.0% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

100

Now

Patch today or shut off access.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 100.0%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Dec 10, 2021. That signals real attacks, not theory.

Remediation deadline for government agencies: Dec 24, 2021.

Known to be used in ransomware campaigns.

Affected systems

VendorProduct
apachelog4j
siemens6bk1602-0aa12-0tp0 firmware
siemens6bk1602-0aa12-0tp0
siemens6bk1602-0aa22-0tp0 firmware
siemens6bk1602-0aa22-0tp0
siemens6bk1602-0aa32-0tp0 firmware
siemens6bk1602-0aa32-0tp0
siemens6bk1602-0aa42-0tp0 firmware
siemens6bk1602-0aa42-0tp0
siemens6bk1602-0aa52-0tp0 firmware
siemens6bk1602-0aa52-0tp0
siemenssppa-t3000 ses3000 firmware

and 154 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache log4j2.13.0 and later · before 2.15.0
  • apache log4j2.0.1 and later · before 2.3.1
  • apache log4j2.4.0 and later · before 2.12.2
  • apache log4j2.0
  • apple xcodebefore 13.3
  • bentley synchro6.1 and later · before 6.2.4.2
  • bentley synchro 4dbefore 6.4.3.2
  • cisco advanced malware protection virtual private cloud appliancebefore 3.5.4
  • cisco automated subsea tuningbefore 2.1.0
  • cisco automated subsea tuning02.01.00
  • cisco broadworksbefore 2021.11_1.162
  • cisco broadworksall versions
  • cisco business process automation3.1.000.000 and later · before 3.1.000.044
  • cisco business process automationbefore 3.0.000.115
  • cisco business process automation3.2.000.000 and later · before 3.2.000.009
  • cisco cloud connectbefore 12.6\(1\)
  • cisco cloudcenterbefore 4.10.0.16
  • cisco cloudcenter cost optimizerbefore 5.5.2
  • cisco cloudcenter suite4.10.0.15
  • cisco cloudcenter suite5.3.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Log4j2

    • 2.0-beta9 and later · before log4j-core*affectedfixed in 2.3.1, 2.12.2, 2.15.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10apache-log4j2before 2.15.0-1~deb10u12.15.0-1~deb10u1
Debian:11apache-log4j2before 2.15.0-1~deb11u12.15.0-1~deb11u1
Debian:12apache-log4j2before 2.15.0-12.15.0-1
Debian:9apache-log4j2before 2.7-2+deb9u12.7-2+deb9u1
Mavencom.guicedee.services:log4j-coreup to and including 1.2.1.2-jre17—
Mavenorg.apache.logging.log4j:log4j-corefrom 2.0-beta9 · before 2.3.12.3.1
Mavenorg.apache.logging.log4j:log4j-corefrom 2.13.0 · before 2.15.02.15.0
Mavenorg.apache.logging.log4j:log4j-corefrom 2.4 · before 2.12.22.12.2
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.10.0 · before 1.10.81.10.8
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.11.0 · before 1.11.101.11.10
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.8.0 · before 1.9.21.9.2
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 2.0.0 · before 2.0.112.0.11
Mavenorg.xbib.elasticsearch:log4jall versions—
Mavenuk.co.nichesolutions.logging.log4j:log4j-coreall versions—
openSUSE:Leap 15.2disruptorbefore 3.4.4-lp152.2.3.13.4.4-lp152.2.3.1
openSUSE:Leap 15.2jakarta-servletbefore 5.0.0-lp152.2.15.0.0-lp152.2.1
openSUSE:Leap 15.2log4jbefore 2.13.0-lp152.3.6.12.13.0-lp152.3.6.1
openSUSE:Leap 15.2log4jbefore 2.16.0-lp152.3.9.12.16.0-lp152.3.9.1
openSUSE:Leap 15.2log4jbefore 2.13.0-lp152.3.3.12.13.0-lp152.3.3.1
openSUSE:Leap 15.2logbackbefore 1.2.8-lp152.2.3.21.2.8-lp152.2.3.2
openSUSE:Leap 15.3disruptorbefore 3.4.4-3.3.13.4.4-3.3.1
openSUSE:Leap 15.3jakarta-servletbefore 5.0.0-5.3.15.0.0-5.3.1
openSUSE:Leap 15.3log4jbefore 2.13.0-4.6.12.13.0-4.6.1
openSUSE:Leap 15.3log4jbefore 2.13.0-4.3.12.13.0-4.3.1

+77

Other highest-scoring records for the same primary product.

  • CVE-2021-45046Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attackKEV
    96Now
  • CVE-2017-5645In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another applic
    66This week
  • CVE-2019-17571Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely exe
    60This week
  • CVE-2022-23305SQL injection in JDBC Appender in Apache Log4j V1
    59Plan
  • CVE-2021-44832Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration
    55Plan
  • CVE-2022-23302Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
    54Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Log4j22.12.2Vendor (CNA)
Apache Software Foundation Apache Log4j22.15.0Vendor (CNA)
Apache Software Foundation Apache Log4j22.3.1Vendor (CNA)
Debian:apache-log4j22.15.0-1 · Debian:12Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.12.2Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.15.0Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.3.1Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.10.8Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.11.10Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.9.2Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j22.0.11Package registry (OSV)
openSUSE:disruptor3.4.4-lp152.2.3.1 · openSUSE:Leap 15.2Package registry (OSV)
openSUSE:jakarta-servlet5.0.0-lp152.2.1 · openSUSE:Leap 15.2Package registry (OSV)
openSUSE:log4j2.13.0-lp152.3.3.1 · openSUSE:Leap 15.2Package registry (OSV)
openSUSE:logback1.2.8-lp152.2.3.2 · openSUSE:Leap 15.2Package registry (OSV)
Red Hat:eap7-jackson-databind0:2.8.11.6-2.SP1_redhat_00002.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-atom-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-cdi0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-client0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-crypto0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jackson-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jackson2-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jaxb-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jaxrs0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jettison-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
Red Hat:eap7-resteasy-jose-jwt0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
SUSE:storm1.2.3-3.8.2 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
SUSE:venv-openstack-monasca2.2.2~dev1-11.32.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×5
  • Exploit-DB entry ×3
  • Nuclei detection template ×46
  • Proof-of-concept repository on GitHub ×50

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2023-04-01
Exploit-DB entryremote2021-12-14
Exploit-DB entryremote2021-12-14
Metasploit moduleauxiliary/scanner/http/log4shell_scannerLog4Shell HTTP Scannerauxiliary2021-12-09
Metasploit moduleexploit/linux/http/mobileiron_core_log4shellMobileIron Core Unauthenticated JNDI Injection RCE (via Log4Shell)exploit2021-12-12
Metasploit moduleexploit/multi/http/log4shell_header_injectionLog4Shell HTTP Header Injectionexploit2021-12-09
Metasploit moduleexploit/multi/http/ubiquiti_unifi_log4shellUniFi Network Application Unauthenticated JNDI Injection RCE (via Log4Shell)exploit2021-12-09
Metasploit moduleexploit/multi/http/vmware_vcenter_log4shellVMware vCenter Server Unauthenticated JNDI Injection RCE (via Log4Shell)exploit2021-12-09
Nuclei detection templateNuclei template CVE-2021-45046-DAST —
Nuclei detection templateNuclei template CVE-2021-44228 —
Nuclei detection templateNuclei template CVE-2021-45046 —
Nuclei detection templateNuclei template apache-druid-log4j-rce —

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-1 d
  2. Metasploit-1 d
  3. CISA KEVsame day
  4. Published
  5. TodaySep 29, 2026+1755 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records