SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
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.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from 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.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
81.5 / 100
Exploited
Yes, in VulnCheck KEV
Reports
1
Tactics
2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 14 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 1 day after disclosure.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
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.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 2 cited passagesAIAI-writtenWritten by a language model from the source data on this page. Not reviewed by a person.2
Initial AccessTA0001
Exploit Public-Facing ApplicationT1190Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. claude-haiku-5-5: Remote attacker exploits Log4j2 application over network.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
Command and Scripting InterpreterT1059Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. claude-haiku-5-5: Arbitrary code execution via JNDI lookup.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
0 rules for this CVE · 244 general rules for its techniques
Rules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2021-44832 directly.
CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
From GitHub Security Advisories and OSVSourceSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. GitHub Security Advisories and OSV.
2 packages in 1 ecosystem. Main package: org.apache.logging.log4j:log4j-core.
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 run
Upgrade to
2.13.0 up to 2.17.1
2.17.1
2.4 up to 2.12.4
2.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)
Named in 1 threat reportMachineMachine-matchedFound by keyword or pattern matching over threat-report text. Not reviewed by a person. Exact CVE id found in the report text.
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.
…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…