SOC Advisory: Critical Apache Log4j Vulnerability

Yesterday, 12/10/2021, a critical zero-day vulnerability in Apache Log4j (CVE-2021-44228), a widely used Java logging library, is being leveraged by attackers in the wild – for now, fortunately, primarily to deliver coin miners.

The SOC is fully engaged in building a comprehensive threat advisory, threat hunting queries, and working with several clients on the matter affected by related exploitation attempts observed in their environments.

We will continue to hunt for related Indicators of Compromise throughout client environments and scan for the vulnerability within our clients that have the Vulnerability Management Service.

We can confirm that the Stellar Cyber – BDS platform’s IDS engine has been updated with new IDS signatures that would trigger security detections on exploitation attempts observed in network traffic.

In addition, the CyFlare SOC has also built its threat hunting queries & custom alarm (ATH) rule to trigger a security detection on exploit attempts. The rule has been enabled and successfully operationalized.

Customers of applications leveraging Apache log4j should upgrade to the newest version immediately.

Since the original patch was discovered to be bypassed, in the interest of implementing as many protections against this vulnerability as possible, the following mitigations are also recommended:

  • Disable suspicious outbound traffic, such as LDAP and RMI on server in PANW Firewall
  • Disable JNDI lookup
    • Remove the JndiLookup file in the log4j-core and restart the device
    • Setup spring.jndi.ignore=true

Reference Links:

Should you have any questions or concerns, please place a ticket with the SOC using [email protected] or call 877.729.3527 extension 2.