Log4Shell and Follow-On Log4j Flaws Drove Broad Enterprise Exposure
Active Exploitation · 12 sources · Updated 3mo ago · First seen Feb 2, 2023

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.


