<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cve-2021-44228 on Anything About IT</title><link>https://www.verboon.info/tags/cve-2021-44228/</link><description>Recent content in Cve-2021-44228 on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 14 Dec 2021 21:25:13 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/cve-2021-44228/index.xml" rel="self" type="application/rss+xml"/><item><title>How To Detect the Log4Shell Vulnerability (CVE-2021-44228) with Microsoft Endpoint Configuration Manager</title><link>https://www.verboon.info/2021/12/how-to-detect-the-log4shell-vulnerability-cve-2021-44228-with-microsoft-endpoint-configuration-manager/</link><pubDate>Tue, 14 Dec 2021 21:25:13 +0000</pubDate><guid>https://www.verboon.info/2021/12/how-to-detect-the-log4shell-vulnerability-cve-2021-44228-with-microsoft-endpoint-configuration-manager/</guid><description>&lt;p&gt;Hello there,&lt;/p&gt;
&lt;p&gt;These days everyone is trying to identify devices that are vulnerable to the Log4Shell Vulnerability (CVE-2021-44228). If your only systems management tool is Microsoft Endpoint Configuration Manager this blog is for you.&lt;/p&gt;
&lt;p&gt;You can of course create device collections based on installed programs, however log4j-core.jar files can be found in several locations in and outside the Program files folder. So in order to identify these files, we have to search for them on the entire disk. Here&amp;rsquo;s the script I prepared for that.&lt;/p&gt;</description></item></channel></rss>