US CISA ordered federal agencies to address the critical Log4Shell vulnerability in the Log4j library by December 24th, 2021. The order aims at preventing threat actors could exploit the vulnerability in attacks against government systems.
The CVE-2021-44228 flaw made the headlines last week, after Chinese security researcher p0rz9 publicly disclosed a Proof-of-concept exploit for the critical remote code execution zero-day vulnerability (aka Log4Shell) that affects the Apache Log4j Java-based logging library.
The impact of the issue is devastating, thousands of organizations worldwide are potentially exposed to attacks and security experts are already reported exploitation attempts in the wild.
The list includes the issues frequently used as an attack vector by threat actors in the wild and that pose significant risk to the federal enterprise.
The US agency also published an “Apache Log4j Vulnerability Guidance” that includes technical details about the vulnerability and provides and mitigation guidance.
“CISA and its partners, through the Joint Cyber Defense Collaborative, are tracking and responding to active, widespread exploitation of a critical remote code execution vulnerability (CVE-2021-44228) affecting Apache Log4j software library versions 2.0-beta9 to 2.14.1. Log4j is very broadly used in a variety of consumer and enterprise services, websites, and applications—as well as in operational technology products—to log security and performance information.” reads the announcement published by CISA. “CISA urges organizations to review its Apache Log4j Vulnerability Guidance webpage and upgrade to Log4j version 2.15.0, or apply the appropriate vendor recommended mitigations immediately.”
CISA also recommends 3 immediate actions:
In accordance with BOD 22-01, US CISA orders federal civilian executive branch agencies to address the Log4Shell by December 24, 2021.
The US CISA recommends affected entities:
log4j2.formatMsgNoLookupsto true by adding
-Dlog4j2.formatMsgNoLookups=Trueto the Java Virtual Machine command for starting your application. Note: this may impact the behavior of a system’s logging if it relies on Lookups for message formatting. Additionally, this mitigation will only work for versions 2.10 and above.
(SecurityAffairs – hacking, Log4Shell)