Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache / Log4j2 · Apache Software Foundation / Apache Log4j2
Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 3 of 4 PoC sources: exploitdb, metasploit, and nuclei.
CPE names NVD's analysts give as vulnerable: a:cisco:unified_communications_manager, a:cisco:unified_communications_manager_im_&_presence_service, a:cisco:unified_communications_manager_im_and_presence_service
CPE names NVD's analysts give as vulnerable: a:cisco:secure_firewall_threat_defensethe product type of Cisco Firepower Threat Defense in nday's product registry
CPE names NVD's analysts give as vulnerable: a:cisco:unified_communications_manager, a:cisco:unified_communications_manager_im_&_presence_service, a:cisco:unified_communications_manager_im_and_presence_service, a:cisco:webex_meetings_serverthe product type of Cisco Unified Communications Manager and Webex in nday's product registry
CPE names NVD's analysts give as vulnerable: a:cisco:identity_services_enginethe product type of Cisco Identity Services Engine in nday's product registry
CPE names NVD's analysts give as vulnerable: a:apache:log4jthe product type of Apache Log4j in nday's product registry
stage
KEV
disclosed
disclosure → PoC
T+4d POC is date-only
cvss
10.0 CRITICAL v3.1
KEV due date
2021-12-24
# Lifecycle
x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
2021-12-14, date only +2 more
metasploit, nuclei
ITWexploited
≤ 2021-12-10, inferred from KEV
KEVKEV
2021-12-10, date only
# Summary
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.
Original text of the CVE record (cvelist), shown as published.
# Exploit conditions
What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.
# Event log
+DISdisclosed
CVE record published by apache. CVSS 10, critical. CISA's SSVC assessment rates exploitation as active.
{
"id": 1483,
"type": "kev_added",
"source": "kev",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
"occurred_at": "2021-12-10T00:00:00Z",
"observed_at": "2026-11-12T13:53:00.018191Z",
"is_backfill": true,
"dedupe_key": "",
"detail": {
"cwes": [
"CWE-20",
"CWE-400",
"CWE-502"
],
"notes": "https://nvd.nist.gov/vuln/detail/CVE-2021-44228",
"product": "Log4j2",
"due_date": "2021-12-24",
"precision": "day",
"date_added": "2021-12-10",
"vendor_project": "Apache",
"forensic_triage": "No",
"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.",
"vulnerability_name": "Apache Log4j2 Remote Code Execution Vulnerability",
"known_ransomware_campaign_use": "Known"
}
}
≤ 2021-12-10inferred, no direct source
~ITWexploited in the wild
No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.
Metasploit has module exploit/linux/http/mobileiron_core_log4shell (MobileIron Core Unauthenticated JNDI Injection RCE (via Log4Shell)). The source gives no release time for the module.
Metasploit has module exploit/multi/http/log4shell_header_injection (Log4Shell HTTP Header Injection). The source gives no release time for the module.
Metasploit has module exploit/multi/http/ubiquiti_unifi_log4shell (UniFi Network Application Unauthenticated JNDI Injection RCE (via Log4Shell)). The source gives no release time for the module.
Your account is suspended: you cannot comment, reply, edit or report. You can still delete your own comments.
formatting
↵↵
empty line: new paragraph
↵
line break: kept as is
*…*
emphasis
**…**
bold
`…`
inline code
```
on its own line: starts and ends a code block
> …
quote
- …
list
1. …
numbered list
[…](https://…)
link (http and https only)
https://…
bare address: link
CVE-2026-1234
links to that vulnerability on nday
\*
shows the character itself
Headings, images, tables, nested lists and HTML are shown as plain text.
Links from new accounts are shown as plain text; CVE IDs are always linked.
reported
# Keyboard shortcuts
j / k
next / previous row (list rows or events)
Enter
open the vulnerability under the cursor
/
search (Esc leaves the box)
y
copy the CVE ID
o
open the event's source (vulnerability page)
u
back
?
show / hide this help
sign inaccountmodadminAdminProfileFollowingSecurityDeveloperSign outSigned in.Sign-in method linked to your account.Sign-in was cancelled at the provider; nothing changed.That login already belongs to another nday account, or this account already has one from the same provider. Nothing was linked.Sign-in did not complete. Try again.You are still signed in as before: that login belongs to another nday account, or to none yet. Sign out first to use it.Linking was not completed because your last sign-in is no longer recent. Confirm it's you on the account page, then link again.This account is suspended, so new sign-in methods cannot be linked.Dismissworking…Delete this comment? This cannot be undone.Hidden by a moderator: {reason}text (moderators only)earlier versions: {n}replaced at {time}Posting needs the community rules accepted (version {version}).The community rules changed (version {version}); read and accept them to continue.Reported. A moderator will look at it.You have already reported this comment.You are signed out. Sign in again to continue.The request was refused as cross-site. Reload the page and try again.The session token changed. Reload the page and try again.Your account is suspended.Choose a handle on your account page first.Accept the current community rules first.Only moderators can do this.Only the author can do this.You cannot report your own comment.This comment changed in the meantime. Reload the page to see it as it is now.This comment or vulnerability does not exist (any more).Not a valid CVE ID.Only a visible top-level comment can get replies.This thread has reached its reply limit.You posted the same text here a moment ago.A comment needs 1 to {max} characters.Comments cannot be posted from this site language.Unknown purpose, or a purpose on a reply. Reload the page and try again.The reason is missing or too long.The note is too long.Unknown resolution.This position in the list is no longer valid. Reload the page.The request was malformed. Reload the page and try again.The text is too large.Too many requests. Try again in {seconds} s.Too many requests. Try again later.Daily limit reached. Try again after {time}.The server is busy. Try again in a moment.This address does not take comments. Open the page on the main site.Server error. Try again later.Network error: nday could not be reached. Check the connection and try again.The community rules changed while you were reading. Read them again.Write something first.Too long: {n} characters, at most {max}.Tick the box to accept the community rules first.Something went wrong ({code}). Try again.No comments yet.The discussion could not be loaded right now.more commentsfirst commentsmore repliesreplies[deleted account]link to this commenteditedposted on the {language} siteHidden by a moderator.Deleted by its author.technical analysisreproduction reportfix reportdetection methodquestionPlease include the affected version, the environment (OS, configuration), what you did and what happened, and your source.Please include the fixed version or patch, the environment, how you checked the fix and what happened, and your source.show {n} moreview on XThe posts could not be loaded.nday has not collected any post on X by listed researchers that mentions this CVE.expandcollapsesending…Sent. An editor will look at it; you can follow its status here.titlesummaryaffected products or versionsfix informationtimeline eventsource linksotherwaiting for an editoracceptednot acceptedsent {at}Editors' note: {note}Sign in first.Your account is suspended.Choose a public handle on your account page first.Accept the current community rules on your account page first.The page's session expired; try again.The request was refused; reload the page and try again.Choose what is wrong.Write what is wrong, within the length limit.The evidence link must be a full http:// or https:// address.You already have several reports on this vulnerability waiting for an editor; wait until they are handled.This vulnerability already has many reports waiting for an editor; try again later.You reached the limit of reports for 24 hours; try again later.Too many requests; wait a moment and try again.This vulnerability was not found.The report is too large.Network error; try again.Write what is wrong first.Too long: at most {max} characters.Something went wrong; try again later.