Critical Log4Shell Remote Code Execution Drives Urgent Log4j Remediation
Vulnerability Disclosure · 14 sources · Updated 3mo ago · First seen Feb 20, 2022

The Dutch National Cyber Security Centre (NCSC) issued a HIGH/HIGH warning for the Apache Log4j/Log4Shell flaws, led by remote-code-execution vulnerabilities including CVE-2021-44228 and CVE-2021-45046. Applications that log attacker-controlled input can allow remote execution with web-server privileges, creating a material risk of major disruption and ransomware. Public exploit techniques, Log4j’s deep presence in third-party products, and incomplete asset visibility made vulnerable deployments difficult to identify; the NCSC reported limited active abuse but expected continued scanning and targeted attacks.
Organizations were urged to inventory direct and supply-chain use of Log4j 2, promptly apply vendor patches, and isolate, mitigate, or disable unpatchable internet-facing systems that process untrusted input. The NCSC advised prioritizing versions affected by the earlier RCE flaws—2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0—and updating from 2.15 to 2.16 and subsequently to current Apache releases, including 2.17.0 where applicable for later issues such as CVE-2021-45105. It also called for log review and threat hunting from at least 1 December, forensic preservation, tested offline backups, segmentation, restricted outbound access, and use of its GitHub repository for affected-product tracking, indicators, detection rules, scanning, and mitigation guidance.


