US Emergency Directive Orders Govt Agencies to Patch Log4j Bug

US Federal Civilian Executive Branch agencies have been ordered to patch the critical and actively exploited Log4Shell security vulnerability in the Apache Log4j library within the next six days.

The order comes through an emergency directive issued by the Cybersecurity and Infrastructure Security Agency (CISA) today.

This is not surprising given the risk the ongoing exploitation of this vulnerability poses and seeing that the security flaw (tracked as CVE-2021-44228) has also recently been added Known Exploited Vulnerabilities Catalog, which also required expedited action in mitigating the bug until December 24.

Also Read: Don’t Be Baited! 5 Signs of Phishing in Email

“To be clear, this vulnerability poses a severe risk. We will only minimize potential impacts through collaborative efforts between government and the private sector. We urge all organizations to join us in this essential effort and take action,” CISA Director Jen Easterly said at the time.

Log4Shell mitigation required until December 23

The new emergency directive (ED 22-02) further requires federal agencies to find all Internet-exposed devices vulnerable to Log4Shell exploits, patch them if a patch is available, mitigate the risk of exploitation, or remove vulnerable software from their networks until December 23.

CISA also says that all devices running software vulnerable to Log4Shell attacks should be assumed to be already compromised and requires looking for signs of post-exploitation activity and monitoring for any suspicious traffic patterns.

The federal agencies were also given five more days, until December 28 to report all affected Java products on their networks, including application and vendor names, the app’s version, and the action taken to block exploitation attempts.

“Although ED 22-02 applies to FCEB agencies, CISA strongly recommends that all organizations review ED 22-02 for mitigation guidance,” CISA added today.

Also Read: 4 Reasons to Outsource Penetration Testing Services

We are working with key private & public partners via #JCDC & federal partners like @FBI & @NSACyber to manage this evolving threat. We will continue to update our consolidated Log4j webpage with the latest info to help all orgs reduce their risk: https://t.co/qlZw2rh8y8

— Jen Easterly (@CISAJen) December 17, 2021

Log4Shell mitigation guidance

Earlier this week, CISA published a dedicated page with technical details regarding the Log4Shell flaw and patching information for impacted organizations.

CISA asks organizations to upgrade to Log4j version 2.16.0 or immediately apply appropriate vendor-recommended mitigations.

The list of actions organizations using products exposed to attacks using Log4Shell exploits includes:

• Reviewing Apache’s Log4j Security Vulnerabilities page for additional information.
• Applying available patches immediately. See CISA’s upcoming GitHub repository for known affected products and patch information.
• Conducting a security review to determine if there is a security concern or compromise. The log files for any services using affected Log4j versions will contain user-controlled strings.
• Reporting compromises immediately to CISA and the FBI

CISA’s push for urgently patching systems vulnerable to Log4Shell attacks follows threat actors’ head start in exploiting Log4Shell vulnerable systems to deploy malware.

As we previously reported, these attacks have been orchestrated by financially-motivated attackers who injected Monero miners, state-backed hackers, and even ransomware gangs [1, 2].

Following reporting of Log2Shell’s ongoing exploitation in widespread attacks, we have also published several dedicated articles sharing a list of vulnerable products and vendor advisories, the reason why you must upgrade to Log4j2.16.0 immediately, as well as more information on the Log4Shell vulnerability.