Huntress Warns of Active Log4j RCE Exploitation and Recommends Version 2.17.1

· Original article ↗

Summary

Huntress reported active exploitation of Log4Shell (CVE-2021-44228), explained its JNDI-based RCE path, and advised updating Log4j to 2.17.1. It warned that bundled software may depend on vendor updates and that a negative test result does not guarantee patching.

Key points

  • The article reported active exploitation of CVE-2021-44228, which affects the Java logging library Log4j and can enable remote code execution.
  • A crafted string in logged input can trigger a vulnerable Log4j instance to make a JNDI request and retrieve attacker-controlled code.
  • Huntress described a Minecraft server proof of concept in which a single chat message could trigger code execution on players' machines.
  • GreyNoise was monitoring exploitation from more than 100 hosts at the time of writing; the article also noted payloads using JNDI DNS as well as LDAP.
  • Huntress recommended Log4j 2.17.1 and warned that software bundling Log4j may require vendors to issue their own updates. It also identified UniFi Controller 6.5.54 as a patched version, based on information shared with Huntress by an MSP community member.
  • The update said Log4j 2.17.1 limits JNDI data source names to the Java protocol to fix an arbitrary-code-execution issue in 2.17.0; earlier updates covered the DoS vulnerability CVE-2021-45105 and Log4j 2.16.0.
  • Huntress offered a testing tool, but cautioned that a negative result does not guarantee an application is patched.

Article Details

Vulnerability Types
  • Remote code execution
  • Denial of service
  • Arbitrary code execution
Severity
Critical
Affected Versions
  • log4j 2.16.0
  • log4j 2.17.0
Exploitation Status
active
Exploit Availability
public_poc
Patch Status
partial

MITRE ATT&CK

CVE

People

Vendors

Products

Tools

Related Articles