Apache Log4j2 versions 2.0-alpha1 through 2.16.0 did not protect from uncontrolled recursion from self-referential lookups. When the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginId}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup, resulting in a StackOverflowError …
Category: Vulnerability Management
Dec 14
Veeam is not affected by Log4J vulnerability
Apache isn’t used by any Veeam product, however, the Veeam security team realized an investigation. Veeam products are not affected by this vulnerability (KB 4254). Basically, Apache Logs4J is not in use by any Veeam products. I’ll cross-post any important updates but you can see the thread yourself here.
Dec 13
Log4J Recommendations – Step by Step Guide
If you’re using any software running on Apache and Java, be aware of this critical zero-day vulnerability. Log4j is a ubiquitous logging tool included in almost every Java application, meaning this vulnerability affects literally millions of servers. The Log4J library vulnerability (CVE-2021-44228) allows an attacker to cause the target system to fetch and execute code …
Follow me
Christopher Glémot is a Data Management & Security Team Leader. Owner of Original-Network.com – Waves of Data.
This blog is mainly focused on Data Management, Security, Backup, Disaster Recovery, Virtualization, Storage, Cloud and Vulnerability Management, but also covers Active Directory.
You can find detailed how-to procedures, tutorials and product reviews.
