The Log4j vulnerability has triggered global headlines. MSPs, MSSPs and security pros are racing to mitigate the vulnerability before more hackers exploit the widespread security issue. Here's how the Log4j vulnerability was discovered, reported, exploited and mitigated, according to ongoing reports from CyberRisk Alliance brands (ChannelE2E, MSSP Alert and SC Media) and third-party reports.
Note: This CISA guidance offers concise advice on how MSPs and MSSPs can mitigate the Log4j vulnerability.
Here's our ongoing timeline of coverage. Keep checking backup for more updates.
Thursday, January 6, 2022: Two cybersecurity experts, Beau Woods and Adam Bregenzer, have developed an open source search tool to help cybersecurity professionals navigate an increasingly cumbersome list of software products affected by the Log4j vulnerability. Source: SC Media.
Tuesday, January 4, 2022: The FTC is warning companies to remediate the Log4j vulnerability in order to "reduce the likelihood of harm to consumers, and to avoid FTC legal action." Source: FTC.
Monday, January 3, 2022: Microsoft on January 3 updated its guidance for preventing, detecting and hunting Log4j vulnerabilities. Source: Microsoft.
Wednesday, December 29, 2021: Multiple updates...
Tuesday, December 28, 2021: Checkmarx, an application security testing firm, discovered a way to use Log4j to launch malicious code, forcing yet another round of patching for affected users. The latest issue, which was considered less severe compared to the earlier Log4j issues -- was patched in Log4j 2.17.1, 2.12.4, and 2.3.2. Source: SC Media.
Monday, December 27, 2021: Multiple updates...
Thursday, December 23, 2021: Alibaba conceded it was slow to report the Log4j vulnerability because it was unaware of its severity, a day after China’s tech industry overseer suspended cooperation on cybersecurity with the online retail giant. Source: Bloomberg.
Wednesday, December 22, 2021: Fully 10% of all assessed assets are vulnerable to Log4Shell, and 30% of organizations haven’t even begun looking for this bug. Source: Tenable.
Friday, December 17, 2021: Multiple updates...
Wednesday, December 15, 2021: Multiple updates...
Tuesday, December 14, 2021: Multiple updates...
Monday, December 13, 2021:
Sunday, December 12, 2021: ChannelE2E tracks MSP software company statements about the vulnerability. The regularly updated coverage includes statements from Auvik Networks, ConnectWise, Datto, Kaseya, Liongard, N-able, NinjaOne and Pax8. Source: ChannelE2E.
Saturday, December 11, 2021: Cybersecurity and Infrastructure Security Agency (CISA) Director Jen Easterly releases a statement about Log4j, and offers some initial mitigation guidance. She notes that the vulnerability poses a "severe risk." Source: MSSP Alert.
Friday, December 10, 2021: Multiple updates...
Friday, November 26, 2021: The date the vulnerability is first recorded into the CVE list. Source: CVE.
Wednesday, November 24, 2021: The Log4j vulnerability is disclosed to Apache by Chen Zhaojun of Alibaba Cloud Security Team. Source: Cyber Kendra.
Keep checking backup for more updates.