Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityinternet-facing-service-vulnerabilityproof-of-concept-releasedetection-content-update

Critical Log4Shell Remote Code Execution Drives Urgent Log4j Remediation

Vulnerability Disclosure · 14 sources · Updated 3mo ago · First seen Feb 20, 2022

Critical Log4Shell Remote Code Execution Drives Urgent Log4j Remediation

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.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

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

12 events · Feb 20, 2022
  1. Reported Dec 16, 20242y ago

    Researchers demonstrate Log4j-based vCenter post-exploitation techniques

    Researchers described exploiting VMware vCenter's Log4j exposure through a JNDI/LDAP payload placed in the X-Forwarded-For header, targeting the /websso/SAML2/SLO/vsphere.local request path to obtain a reverse shell. They also demonstrated capturing Base64-encoded CastleAuthorization credentials from Envoy authentication traces and adapting tooling to use stolen vmware_soap_session tokens with pyVmomi for remote VM command execution.

    How to Leverage Log4j to Expose vCenter Attack Paths - Part 1 - Cymulate
  2. Feb 20, 20225y ago

    NCSC renews warning to remain vigilant for Log4j exploitation

    On 20 February 2022, NCSC-NL warned that the high-risk Log4j vulnerabilities remained difficult to identify because the library was embedded in many products and systems. Although rapid remediation appeared to have limited active exploitation, it expected continued scanning and targeted attacks and urged continued identification and patching or mitigation of vulnerable systems.

    Houd aandacht voor Log4j | NCSC
  3. Reported Dec 23, 20215y ago

    NCSC develops Log4j response plan and mitigation overview

    NCSC-NL updated its advisory as vulnerabilities and remediations evolved, created a mitigation-and-effects overview, and developed a response plan for organizations. It also maintained its GitHub collection of vulnerable software, detection rules, indicators, scanning resources, and mitigations, and conducted webinars and meetings with Dutch government, vital-sector, CERT, and OKTT participants.

    Log4j - blijf alert, ook tijdens de feestdagen | NCSC
  4. Reported Dec 21, 20215y ago

    Apache releases Log4j 2.17.1 for CVE-2021-44832

    Apache released Log4j 2.17.1 to address CVE-2021-44832, a configuration-file-dependent remote-code-execution vulnerability affecting versions 2.0-alpha7 through 2.17.0, with exceptions for 2.3.2 and 2.12.4. The flaw was rated 6.6 because exploitation required an attacker to modify the Log4j configuration file.

    Log4Shell: Wrap all your Log4j fixes before the holidays | Wiz Blog
  5. Reported Dec 18, 20215y ago

    NCSC updates Log4j guidance for CVE-2021-45105

    NCSC-NL updated its advisory for CVE-2021-45105, assessing it as less severe than the earlier remote-code-execution flaws. It advised prioritizing remediation of RCE-affected versions and then upgrading applications from Log4j 2.16.0 to 2.17.0.

    Kwetsbaarheid Log4j versie 2.16 | NCSC
  6. Reported Dec 17, 20215y ago

    NCSC updates advisory for an additional Log4j 2.15 vulnerability

    NCSC-NL issued an updated NCSC-2021-1052 advisory concerning an additional Log4j vulnerability affecting the 2.15 line. It directed organizations to Apache's updated releases and reiterated the need to prepare for potential abuse.

    Aanvullende kwetsbaarheid Log4j versie 2.15 | NCSC
  7. Reported Dec 15, 20215y ago

    NCSC recommends upgrading Log4j 2.14 and 2.15 to version 2.16

    NCSC-NL urged organizations using Log4j 2.14 or earlier to upgrade as soon as possible to version 2.16, and recommended that users of 2.15 also upgrade where possible. It updated advisory NCSC-2021-1052 and said it continued receiving reports of limited active abuse.

    Kwetsbaarheid in Apache Log4j patch versie 2.15 | NCSC
  8. Reported Dec 15, 20215y ago

    NCSC publishes expanded Log4j exploitation-preparedness guidance

    NCSC-NL advised organizations to inventory Log4j v2 use, urgently apply supplier patches, mitigate or disable unpatchable exposed systems, and investigate for exploitation dating back at least to 1 December. Its guidance also covered incident-response readiness, forensic preservation, detection, backups, segmentation, restricted outbound traffic, and supplier dependencies.

    Log4j - bereid u voor op misbruik | NCSC
  9. Reported Dec 13, 20215y ago

    NCSC reports limited Log4j exploitation in the Netherlands

    NCSC-NL reported observing limited active exploitation in the Netherlands, while cautioning that the vulnerability's nature made exploitation difficult to track. It assessed that abuse could cause major consequential damage and updated its response guidance.

    Log4j kwetsbaarheid: bereid u voor op misbruik | NCSC
  10. Reported Dec 12, 20215y ago

    NCSC treats vulnerable-software listings as advisory updates

    NCSC-NL said it could not issue a separate advisory update for every Log4j-using application and that inclusion on its list constituted an update to the HIGH/HIGH advisory. It published an overview page with recommended response steps for organizations.

    UPDATE: Kwetsbare Log4j applicaties en te nemen stappen | NCSC
  11. Reported Dec 11, 20215y ago

    NCSC issues HIGH/HIGH Log4j advisory and vulnerable-applications list

    NCSC-NL issued a HIGH/HIGH advisory for the severe Apache Log4j flaw, warning that publicly known exploitation methods could enable remote abuse of vulnerable web-server privileges. It also published an initially incomplete GitHub list of affected applications and sought community contributions, detection resources, and indicators of compromise.

    UPDATE: Installeer updates tegen ernstige kwetsbaarheid in Apache Log4j | NCSC
  12. Reported Dec 10, 20215y ago

    Wiz reports widespread Log4Shell exposure and an affected NSA tool

    Wiz reported that exploitation of CVE-2021-44228 was active and estimated that more than 89% of environments contained vulnerable Log4j libraries. It also stated that the NSA reverse-engineering tool was vulnerable, and described JNDI/LDAP payloads that could cause a vulnerable server to retrieve and execute attacker-supplied Java code.

    Log4Shell Meltdown: How to protect your cloud from this critical RCE threat | Wiz Blog
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 →

Observables

7 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?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
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.