Patchfirst
CVE-2021-44832 Public exploit Medium · 6.6 EPSS 97.9%

Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

Apache Software Foundation · Apache Log4j2

Summary

Apache Log4j2, from the Apache Software Foundation, contains a flaw in its JDBC Appender where a JNDI LDAP data source URI in the logging configuration is processed without adequate validation. An attacker who controls the target LDAP server can achieve remote code execution, but only when the configuration uses a JDBC Appender with such a JNDI LDAP data source, and the affected versions span 2.0-beta7 through 2.17.0, excluding the security fix releases 2.3.2 and 2.12.4.

Official description · CVE.org

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.

Breakdown
81.5 / 100
Exploited
Yes, in VulnCheck KEV
Reports
1
Tactics
2/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

First seen exploited 14 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 1 day after disclosure.

  1. Disclosedday 0
  2. Public exploit codePoC-in-GitHub+1 day
  3. First seen exploitedVulnCheck KEV evidence+14 mo

7 fixes in log4j-core over 4 years. The latest fix listed for log4j-core is 2.25.4.

Fixes in log4j-coreMaven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 2.15.0CVE-2021-4422810 Dec 2021KEV
  2. 2.16.0CVE-2021-4504614 Dec 2021KEV
  3. 2.17.0CVE-2021-4510518 Dec 2021
  4. 2.17.1CVE-2021-4483228 Dec 2021
  5. 2.25.3CVE-2025-6816118 Dec 2025
  6. 2.25.4CVE-2026-3447710 Apr 2026
  7. 2.25.4CVE-2026-3447810 Apr 2026Latest listed

techniques

2 , grouped by in kill-chain order, 2 cited passages 2

Initial AccessTA0001

Exploit Public-Facing Application T1190 Medium
AI mapping from the description · how it is exploited

Remote attacker exploits Log4j2 application over network

remote code execution (RCE) attack when a configuration uses a JDBC Appender
From the official description (CVE.org) Original (opens in a new tab) ↗

ExecutionTA0002

Command and Scripting Interpreter T1059 Medium
AI mapping from the description · primary impact

Arbitrary code execution via JNDI lookup

remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP
From the official description (CVE.org) Original (opens in a new tab) ↗

Detection

0 rules for this CVE · 244 general rules for its techniques

Rules for this CVE

0 that reference CVE-2021-44832 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

2 packages in 1 ecosystem. Main package: org.apache.logging.log4j:log4j-core.

Mavenorg.apache.logging.log4j:log4j-coreGHSA-8489-44mv-ggj8

Upgrade to 2.17.1 or later

Fixes this CVE and 3 other known vulnerabilities in this package (CVE-2021-44228, CVE-2021-45046, +1).

Set the version to 2.17.1 or later in your pom.xml or build.gradle.

The first fix for CVE-2021-44832.

Affected versions, by release line

If you runUpgrade to
2.13.0 up to 2.17.12.17.1
2.4 up to 2.12.42.12.4
2.0-beta7 up to 2.3.2

Still affected on this line by CVE-2017-5645 (fixed in 2.8.2, a newer line).

2.3.2

“Up to” means the second version is the fix and is not affected.

Other packages that bundle this code (1)

Forks, repackagings and products that include the affected code. Each has its own fixed version.

  • Mavenorg.ops4j.pax.logging:pax-logging-log4j2
    Affected: 2.0.0 up to 2.0.14; 1.11.0 up to 1.11.13; 1.10.0 up to 1.10.9; 1.8.0 up to 1.9.2Upgrade to 2.0.14 or later (older lines: 1.11.13, 1.10.9, 1.9.2)

Check your lockfile against all CVEs

What security researchers reported

Named in 1 threat report
1 reportLinkedIn

Reports are matched by finding the exact id CVE-2021-44832 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.

LinkedInUndated

RaaS AvosLocker Incident Response Analysis

…vulnerabilities associated to Log4J were found on the VMWare Horizon Unified Access Gateways, UAG01 and UAG02, those were CVE-2021-44228 / CVE-2021-45046 / CVE-2021-45105 / CVE-2021-44832, which can potentially allow remote code execution on Unified Access Gateway by the low privilege non-root user named…

Original (opens in a new tab) ↗

Also mentioned in 29 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

12 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close