Skip to main content
Mallory
← Back to News
actively-exploited-vulnerabilityopen-source-dependency-vulnerabilityrapid-weaponizationwidely-deployed-product-advisory

Log4Shell and Follow-On Log4j Flaws Drove Broad Enterprise Exposure

Active Exploitation · 12 sources · Updated 3mo ago · First seen Feb 2, 2023

Log4Shell and Follow-On Log4j Flaws Drove Broad Enterprise Exposure

Apache Log4j remained at the center of a major software supply chain security crisis after Log4Shell (CVE-2021-44228) exposed Java applications to remote code execution through crafted requests that could force vulnerable systems to retrieve and run attacker-controlled payloads. The flaw affected Log4j 2.0-beta9 through 2.14.1, was reported as easy to exploit, and was observed in widespread attacks across enterprise networks, prompting urgent calls to identify exposed assets and apply vendor fixes or mitigations.

Remediation proved more complex as Apache issued updates and additional Log4j vulnerabilities emerged, including CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832, raising concerns that patching alone would not address prior compromise or attacker persistence. Organizations were pushed to combine software updates with threat hunting and incident response, while defenders also relied on community tracking of affected products through resources such as CISA's log4j-affected-db, which has since been archived as read-only.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Nov 24, 2021 – Feb 2, 2023
  1. Feb 2, 20234y ago

    CISA archives log4j-affected-db repository

    The cisagov/log4j-affected-db GitHub repository was archived and made read-only, ending active updates to the community-sourced list of Log4j-affected software.

    GitHub - cisagov/log4j-affected-db: A community sourced list of log4j-affected software
  2. Reported Nov 22, 20224y ago

    Elastic publishes Log4Shell exploitation detection and hunting logic

    Elastic Security documented detection and hunting logic for Log4Shell exploitation, including suspicious Java connections to LDAP, RMI, and DNS services; Java-spawned shells or download tools; malicious executable creation; reverse-shell behavior; and cryptomining indicators. It also provided mitigation guidance such as upgrading Log4j, disabling message lookups where supported, and restricting outbound connectivity from vulnerable hosts.

    Detecting Exploitation of CVE-2021-44228 (Log4j2) with Elastic Security | Elastic Security Labs
  3. Feb 11, 20225y ago

    Additional Log4j flaws disclosed after initial fix

    After the Log4j 2.15.0 release, subsequent vulnerabilities CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 were introduced or revealed, showing the initial remediation was incomplete.

    The ultimate cybercriminal gift list: undisclosed zero-day vulnerabilities
  4. Dec 13, 20215y ago

    Log4Shell exploitation reported at global scale

    By December 13, reporting described CVE-2021-44228 as a critical zero-day affecting Log4j 2.0-beta9 through 2.14.1 and said it was being actively exploited against vulnerable systems at scale. The same reporting cited Check Point Software's observation of exploit attempts on more than 31.5% of corporate networks globally.

    Log4j Vulnerability Fix: Comprehensive Log4Shell Resources
  5. Dec 10, 20215y ago

    Apache releases Log4j 2.15.0 to address Log4Shell

    Apache released Log4j version 2.15.0 on December 10 to fix the remote code execution vulnerability CVE-2021-44228 (Log4Shell).

    The ultimate cybercriminal gift list: undisclosed zero-day vulnerabilities
  6. Nov 24, 20215y ago

    Apache privately receives initial Log4Shell report

    Apache received a private report of the Log4Shell remote code execution vulnerability, CVE-2021-44228, before public disclosure and patch release. This marks the earliest explicitly dated event in the reference's account of the vulnerability timeline.

    Patch Now: Apache Log4j Vulnerability Called Log4Shell Actively Exploited | Trend Micro (US)
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

2 linked
Log4jAmazon Web Services

Organizations

6 linked
Valve CorporationAmazon Web ServicesCloudflareX CorpAppleBaidu

Observables

4 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.