Event
Eine Sicherheitslücke in Log4j
In December 2021 a serious vulnerability in the Java logging library Log4j became public. An official report documents disclosure and early exploitation attempts. Source
Under certain conditions the flaw in a widely used software component could enable execution of attacker-supplied code. Apache credits Chen Zhaojun of the Alibaba Cloud Security Team with its discovery. The investigation describes how many organizations initially struggled to identify where vulnerable components were embedded. Project information and investigation
Apache later described the initial fix in version 2.15.0 as incomplete for certain non-default configurations; its separate advisory for CVE-2021-45046 initially described a possible denial of service. Further vulnerabilities and fixes followed. This historical sequence is not a current security assessment. Apache advisory
The official review distinguishes the report to Apache on 24 November 2021, early observed exploit testing from 1 December, and public disclosure on 9 December. Apache dates version 2.15.0 to 6 December and 2.16.0 to 13 December; the sequence illustrates how the assessment evolved during the response. Timeline and release notes
Sources
Zeitgenössische Apache-Meldung zu CVE-2021-45046: zunächst beschriebene Auswirkungen und Einschränkung auf bestimmte Konfigurationen.
Meldung und Korrekturfolge: behördliche Zeitleiste und Apache-Versionshinweise.
Apache-Sicherheitshinweise und behördlicher Untersuchungsbericht: Entdeckung, Abhängigkeiten und Korrekturfolge.
Quellenhinweis: Abschnitt Disclosure Timeline, Dezember 2021.
Offen
Nicht jede Anwendung mit Log4j war in gleicher Weise betroffen; konkrete Version und Konfiguration prüfen.