Log4j Update: Patch Priority, Affected Versions and CVE-2021-44832

· Original article ↗

Summary

Wiz updates its Log4j guidance with CVE-2021-44832 details, patch priorities, affected-version advice, and ways to find vulnerable software. It urges fixing CVE-2021-44228 first because it is easier to exploit and actively exploited.

Key points

  • Apache released Log4j 2.17.1 on December 28, 2021, to address CVE-2021-44832, which affects versions 2.0-alpha7 through 2.17.0, excluding 2.3.2 and 2.12.4.
  • The article says CVE-2021-44832 has a severity rating of 6.6 and requires an attacker to be able to modify the Log4j configuration file.
  • Wiz recommends prioritizing CVE-2021-44228 because it is easier to exploit and was being heavily exploited; it also advises prioritizing publicly exposed and highly privileged workloads.
  • The article reports that 55% of workloads in organizations that had mitigated Log4j vulnerabilities were still vulnerable to Log4Shell as of December 21, 2021.
  • Reported exploitation included Mirai variants, Kinsing, ransomware attempts, and nation-state activity tracked by Microsoft; the article attributes these reports to the named researchers and organizations.
  • Suggested discovery approaches include scanning for log4j-core files, searching internally developed software for Log4j references, and consulting vendor and NCSC-NL affected-software lists.
  • The article recommends upgrading to the latest applicable Log4j version and describes WAF rules and restricting outbound connections as temporary network-level mitigations.

Article Details

Vulnerability Types
  • Remote code execution
  • Denial of service
Severity
CVE-2021-44832 is rated 6.6; the article describes the original Log4Shell vulnerability as 10/10 at disclosure and reports CVE-2021-44228 as critical.
Affected Versions
  • Apache Log4j 2.0-alpha7–2.17.0, excluding 2.3.2 and 2.12.4 (CVE-2021-44832)
  • Apache Log4j versions lower than 2.15.0 (CVE-2021-44228)
  • Apache Log4j 1.x with JMSAppender configured (CVE-2021-4104)
Exploitation Status
active
Exploit Availability
unknown
Patch Status
available
Workarounds
  • Use a network-level WAF to block common attacks while updating affected software.
  • Prevent servers from initiating outbound connections to unknown or black-listed domains.

Indicators of compromise

TypeIndicatorContext
HOSTNAME715de0e31919[.]bingsearchlib[.]comAttacker-controlled LDAP host referenced in the Log4Shell payload example.

MITRE ATT&CK

CVE

Threat Actors

Malware

Vendors

Products

Tools

Countries

Related Articles