Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2021-45105: Uncontrolled Recursion Denial of Service in Apache Log4j2

Published Dec 18, 2021 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.9Medium · v3.1
EPSS100.0%100th percentile
CISA KEVNoNot listed
In the wildReported9 exploitation records in Mallory
Vendors
SonicwallOracle CorporationNetAppDebian ProjectApache Software Foundation
IdentifiersCVE-2021-45105CWE-674 · Uncontrolled Recursion

Apache Log4j2 versions 2.0-alpha1 through 2.16.0, excluding 2.12.3 and 2.3.1, fail to prevent uncontrolled recursion during evaluation of self-referential lookups. When a non-default Pattern Layout contains a Context Lookup, an attacker controlling Thread Context Map data can supply a crafted value that triggers recursive lookup evaluation. This can produce a StackOverflowError and terminate the affected application process, causing denial of service.

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 can disrupt application availability by exhausting the execution stack and terminating the affected process. This vulnerability does not itself establish remote code execution, information disclosure, or integrity compromise; those impacts associated with other Log4j vulnerabilities should not be attributed to CVE-2021-45105.

Mitigation

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

If immediate upgrading is not possible, replace Context Lookups in PatternLayout with Thread Context Map conversion patterns such as %X, %mdc, or %MDC. Alternatively, remove Context Lookup references that resolve externally controlled values, including HTTP headers and other user input. Do not rely on message-lookup disabling flags or removal of JNDI lookup functionality as a fix for this recursive Context Lookup vulnerability.

Remediation

Patch, then assume compromise.

Upgrade Log4j to a supported release containing the fix. The first fixed versions are 2.17.0 for Java 8 or later, 2.12.3 for Java 7, and 2.3.1 for Java 6. For applications bundling Log4j, install the vendor's corresponding fixed product release or security patch. Updating Java alone does not remediate the vulnerable Log4j library. If log4j-api is used alongside log4j-core, keep their versions aligned.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit.

View more in app →
log4shell-corazaThis repository is a defensive Log4Shell lab rather than a standalone offensive exploit drop, but it does contain working exploit components. The structure combines: (1) a vulnerable target container (`log4shell-app`, based on a public Spring Boot Log4j 2.14.1 image), (2) an nginx reverse proxy with the Coraza WAF and OWASP CRS plus custom Log4Shell rules, (3) an attacker container that builds and packages multiple JNDI exploitation toolkits, and (4) Suricata/Wazuh monitoring for network and SIEM visibility. The main exploit capability lives under `attacker/`. `attacker/exploit-classes/Exploit.java` is a malicious Java class intended to be loaded through a JNDI/LDAP reference. Its static initializer executes immediately on class load and performs proof-of-exploitation actions: OS-specific command execution to write a marker file, creation of `/tmp/log4shell-exploited.txt`, and an optional reverse shell routine that connects to `172.20.0.2:4444`. There is also a stubbed environment-information collection method. This makes the repo more than a detector: it includes an actual RCE payload class. `attacker/scripts/start-ldap-server.sh` operationalizes exploitation by launching one of three JNDI infrastructures: marshalsec, JNDI-Exploit-Kit, or rogue-jndi. These are configured to serve the malicious class or execute simple commands/callbacks. `attacker/scripts/test-payloads.sh` is a payload spray/test harness that sends many Log4Shell payload variants to the nginx proxy using common injection points such as `User-Agent` and `X-Forwarded-For`. It includes LDAP, RMI, DNS, nested-expression, env/sys fallback, Unicode, whitespace, and colon-dash obfuscation variants. This script is primarily for validation of WAF/IDS coverage, but it also demonstrates realistic attack strings. The rest of the repository is focused on detection and containment. `coraza/config/log4shell-rules.conf` defines custom Coraza rules for standard and obfuscated JNDI patterns, alternate protocols, JSON/XML body inspection, and anomaly-score blocking. `nginx/` contains a multi-stage Docker build that compiles libcoraza and the coraza-nginx module, installs OWASP CRS, and exposes HTTP/HTTPS reverse proxying to the vulnerable app. `suricata/rules/log4shell.rules` adds network signatures for inbound JNDI payloads and outbound LDAP/RMI/DNS/HTTP callbacks that would indicate successful exploitation. Overall purpose: provide an isolated lab to demonstrate the full Log4Shell attack chain and, more importantly, how nginx+Coraza and Suricata can detect/block it. Because the repository includes a real malicious Java payload and scripts to stand up LDAP/JNDI exploit servers, it should be classified as a valid exploit-capable lab with operational payloads, not merely documentation or a pure detection script.tieupham267 · Disclosed Apr 28, 2026 · markdown · dockerfile · web · networkOperationalCVE-2021-45105-demoThis repository is a minimal proof-of-concept payload set for CVE-2021-45105 affecting Apache Log4j 2. It does not contain executable exploit code, scripts, or framework integration; instead it consists of five text files containing progressively larger recursive lookup expressions intended to be copied into attacker-controlled input that will later be logged by a vulnerable application. The file naming convention reflects payload depth/size: 1, 10, 100, 1000, and 10000 nested expansions. There are no outbound network calls, hardcoded URLs, IPs, domains, filesystem targets, or registry paths in the repository. The exploit capability is denial of service only: if one of these strings is processed by a vulnerable Log4j instance, recursive evaluation can trigger stack exhaustion or similar failure. Structurally, the repository is just a payload corpus for testing or demonstrating the vulnerability severity at different recursion depths.aajuvonen · Disclosed Apr 3, 2022 · text · network · localPoClog4shell-chainThis repository contains standalone, effect-only proof-of-concept reproducers for the Log4j vulnerability family, not a working RCE delivery framework. Its 32 files include three Java main classes, one Python callback recorder, eight Dockerfiles, two GitHub Actions workflows, three case manifests, three Maven build files, four Log4j XML configurations, documentation and ignore rules. The code-file count includes the four application sources, eight Dockerfiles and two executable workflows; Bash occurs inside workflow steps. The original repository URL, analyzed ref and archive size were not supplied, so their metadata fields use empty/zero placeholders. Case A compares Log4j 2.14.1, 2.15.0 and 2.16.0 using logged LDAP JNDI strings, with a non-default ThreadContext layout intended to demonstrate CVE-2021-45046. Case B compares 2.16.0 and 2.17.0 using a recursive context value and stack-exhaustion canary. Case C compares 2.17.0 and 2.17.1 using an attacker-controlled JDBC appender configuration. These versions include negative controls and should not all be interpreted as vulnerable to every listed CVE. The Java drivers exercise their own bundled dependencies rather than attacking a supplied remote application endpoint. The Python collaborator listens on TCP 1389 by default, receives up to 4096 bytes with a two-second timeout, closes each connection without replying, and records peer address, timestamp and a 256-byte preview. It serves neither Java classes nor LDAP referrals. Initial LDAP traffic may be a bind request without the token-bearing search DN, so a connection record does not guarantee token correlation or successful RCE. Important correctness limitations prevent accepting the manifests' expected 'proven' verdicts as evidence. Case B uses a plain message containing ${ctx:x} and a %msg layout on Log4j 2.16.0, where message lookups are removed; the supplied configuration therefore lacks an evident path to the claimed recursion. Its external watchdog is also not supplied. Case A's exact 2.15.0 bypass and layout evaluation timing remain unvalidated. Case C's JDBC/JNDI initialization, version-specific enablement and dependency wiring also need validation. A dark callback can reflect configuration failure rather than a successful security fix. NOTES.md and the README explicitly state that builds and live trials remain outstanding, despite other prose describing platform-generated proofs. The cases/*.yaml files are declarative inputs for a separate Tegron platform service; no local prove/assert CLI, proof artifacts or platform implementation is included. prove.yml builds images and prints expected chains but does not execute the trials, and its build steps tolerate failure. A separate Ferralon workflow invokes an external pinned scanner with console linking enabled and explicitly configures /runs and /ingest API destinations. Those destinations are CI integration endpoints, not exploit infrastructure; comments claiming that the workflow names no Ferralon host contradict its actual inputs. No reverse shell, persistence, credential theft or malicious code-loading payload is present.ferralon-demo · Disclosed Jun 23, 2026 · java · python · network · local · filePoC
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
Debian ProjectDebian Linuxoperating_system
NetAppCloud Managerapplication
Oracle CorporationAgile Engineering Data Managementapplication
Oracle CorporationAgile Plmapplication
Oracle CorporationAgile Plm Mcad Connectorapplication
Oracle CorporationAgile Product Lifecycle Managementapplication
Oracle CorporationAutovue For Agile Product Lifecycle Managementapplication
Oracle CorporationBanking Deposits And Lines Of Credit Servicingapplication
Oracle CorporationBanking Enterprise Default Managementapplication
Oracle CorporationBanking Loans Servicingapplication
Oracle CorporationBanking Party Managementapplication
Oracle CorporationBanking Paymentsapplication
Oracle CorporationBanking Platformapplication
Oracle CorporationBanking Trade Financeapplication
Oracle CorporationBanking Treasury Managementapplication
Oracle CorporationBusiness Intelligenceapplication
Oracle CorporationCommunications Asapapplication
Oracle CorporationCommunications Billing And Revenue Managementapplication
Oracle CorporationCommunications Cloud Native Core Consoleapplication
Oracle CorporationCommunications Cloud Native Core Network Function Cloud Native Environmentapplication
Oracle CorporationCommunications Cloud Native Core Network Repository Functionapplication
Oracle CorporationCommunications Cloud Native Core Network Slice Selection Functionapplication
Oracle CorporationCommunications Cloud Native Core Policyapplication
Oracle CorporationCommunications Cloud Native Core Security Edge Protection Proxyapplication
Oracle CorporationCommunications Cloud Native Core Service Communication Proxyapplication
Oracle CorporationCommunications Cloud Native Core Unified Data Repositoryapplication
Oracle CorporationCommunications Convergenceapplication
Oracle CorporationCommunications Convergent Charging Controllerapplication
Oracle CorporationCommunications Diameter Signaling Routerapplication
Oracle CorporationCommunications Eagle Element Management Systemapplication
Oracle CorporationCommunications Eagle Ftp Table Base Retrievalapplication
Oracle CorporationCommunications Element Managerapplication
Oracle CorporationCommunications Evolved Communications Application Serverapplication
Oracle CorporationCommunications Interactive Session Recorderapplication
Oracle CorporationCommunications Ip Service Activatorapplication
Oracle CorporationCommunications Messaging Serveroperating_system
Oracle CorporationCommunications Network Charging And Controlapplication
Oracle CorporationCommunications Network Integrityapplication
Oracle CorporationCommunications Performance Intelligence Centerapplication
Oracle CorporationCommunications Pricing Design Centerapplication
Oracle CorporationCommunications Service Brokerapplication
Oracle CorporationCommunications Services Gatekeeperapplication
Oracle CorporationCommunications Session Report Managerapplication
Oracle CorporationCommunications Session Route Managerapplication
Oracle CorporationCommunications Unified Inventory Managementapplication
Oracle CorporationCommunications User Data Repositoryapplication
Oracle CorporationCommunications Webrtc Session Controllerapplication
Oracle CorporationData Integratorapplication
Oracle CorporationEnterprise Manager Base Platformapplication
Oracle CorporationEnterprise Manager For Peoplesoftapplication
Oracle CorporationEnterprise Manager Ops Centerapplication
Oracle CorporationFinancial Services Analytical Applications Infrastructureapplication
Oracle CorporationFinancial Services Model Management And Governanceapplication
Oracle CorporationFlexcube Universal Bankingapplication
Oracle CorporationHealth Sciences Empirica Signalapplication
Oracle CorporationHealth Sciences Informapplication
Oracle CorporationHealth Sciences Information Managerapplication
Oracle CorporationHealthcare Data Repositoryapplication
Oracle CorporationHealthcare Foundationapplication
Oracle CorporationHealthcare Master Person Indexapplication
Oracle CorporationHealthcare Translational Researchapplication
Oracle CorporationHospitality Suite8application
Oracle CorporationHospitality Token Proxy Serviceapplication
Oracle CorporationHyperion Bi+application
Oracle CorporationHyperion Data Relationship Managementapplication
Oracle CorporationHyperion Infrastructure Technologyapplication
Oracle CorporationHyperion Planningapplication
Oracle CorporationHyperion Profitability And Cost Managementapplication
Oracle CorporationHyperion Tax Provisionapplication
Oracle CorporationIdentity Management Suiteapplication
Oracle CorporationIdentity Manager Connectorapplication
Oracle CorporationInstantis Enterprisetrackapplication
Oracle CorporationInsurance Data Gatewayapplication
Oracle CorporationInsurance Insbridge Rating And Underwritingapplication
Oracle CorporationJdeveloperapplication
Oracle CorporationManaged File Transferapplication
Oracle CorporationManagement Cloud Engineapplication
Oracle CorporationMysql Enterprise Monitorapplication
Oracle CorporationOracle E-Business Suiteapplication
Oracle CorporationOracle Weblogic Serverapplication
Oracle CorporationPayment Interfaceapplication
Oracle CorporationPeoplesoft Enterprise Peopletoolsapplication
Oracle CorporationPrimavera Gatewayapplication
Oracle CorporationPrimavera P6 Enterprise Project Portfolio Managementapplication
Oracle CorporationPrimavera Unifierapplication
Oracle CorporationRetail Back Officeapplication
Oracle CorporationRetail Central Officeapplication
Oracle CorporationRetail Customer Insightsapplication
Oracle CorporationRetail Data Extractor For Merchandisingapplication
Oracle CorporationRetail Eftlinkapplication
Oracle CorporationRetail Financial Integrationapplication
Oracle CorporationRetail Integration Busapplication
Oracle CorporationRetail Invoice Matchingapplication
Oracle CorporationRetail Merchandising Systemapplication
Oracle CorporationRetail Order Brokerapplication
Oracle CorporationRetail Order Management Systemapplication
Oracle CorporationRetail Point-Of-Serviceapplication
Oracle CorporationRetail Predictive Application Serverapplication
Oracle CorporationRetail Price Managementapplication
Oracle CorporationRetail Returns Managementapplication
Oracle CorporationRetail Service Backboneapplication
Oracle CorporationRetail Store Inventory Managementapplication
Oracle CorporationSiebel Ui Frameworkapplication
Oracle CorporationSql Developerapplication
Oracle CorporationTaleo Platformapplication
Oracle CorporationUtilities Frameworkapplication
Oracle CorporationWebcenter Portalapplication
Oracle CorporationWebcenter Sitesapplication
Sonicwall6bk1602-0aa12-0tp0 Firmwareoperating_system
Sonicwall6bk1602-0aa22-0tp0 Firmwareoperating_system
Sonicwall6bk1602-0aa32-0tp0 Firmwareoperating_system
Sonicwall6bk1602-0aa42-0tp0 Firmwareoperating_system
Sonicwall6bk1602-0aa52-0tp0 Firmwareoperating_system
SonicwallEmail Securityapplication
SonicwallNetwork Security Managerapplication
SonicwallWeb Application Firewallapplication
FAQ

Frequently asked questions

Is CVE-2021-45105 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2021-45105?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2021-45105, the earliest disclosed Apr 3, 2022.
Is there a patch for CVE-2021-45105?
Upgrade Log4j to a supported release containing the fix. The first fixed versions are 2.17.0 for Java 8 or later, 2.12.3 for Java 7, and 2.3.1 for Java 6.
What products are affected by CVE-2021-45105?
Apache Software Foundation Log4j, Sonicwall 6bk1602-0aa12-0tp0 Firmware, Sonicwall 6bk1602-0aa22-0tp0 Firmware, Sonicwall 6bk1602-0aa32-0tp0 Firmware, Sonicwall 6bk1602-0aa42-0tp0 Firmware, and at least 112 more.
How severe is CVE-2021-45105?
CVE-2021-45105 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
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 evidence8Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.