How To Detect the Log4Shell Vulnerability (CVE-2021-44228) with Microsoft Endpoint Configuration Manager

Hello there,

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.

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’s the script I prepared for that.

Note that I have intentionally limited the drive letters to a-e, adjust this if you know of systems with more drive letters.

You can find the script here:

The script produces the following output.

Next, import the script into the Microsoft Endpoint Configuration Manager Script library. Then select a device collection and run the script.

Next, we are going to extract the Run Script results with PowerShell. I wrote about this method earlier in this blog post Extract ConfigMgr Script Status Results with PowerShell – Anything about IT (

Open PowerShell from the ConfigMgr console and then load the Export-CMScriptResults function that you copied from the blog post mentioned above or from here: Export-CMScriptResults (

We now have all the results in our PowerShell variable $log4 so we can further review the data

And as a little bonus, let’s compare the identified files with some log4j-core.jar file hash references available on GitHub

The above code snippets can be found here:

If you have a match, it will show the output as following:

I hope you enjoyed this blog post, have a great day and good luck with identifying vulnerable devices.

Credits / References

SCCM scan for Log4J : SCCM (

Log4Shell: RCE 0-day exploit found in log4j 2, a popular Java logging package | LunaSec

mubix/CVE-2021-44228-Log4Shell-Hashes: Hashes for vulnerable LOG4J versions (

log4j2 core jar versions and checksums (

6 Replies to “How To Detect the Log4Shell Vulnerability (CVE-2021-44228) with Microsoft Endpoint Configuration Manager”

  1. Great post Alex but I always got a warning message as I run the line:
    $log4 = Export-CMScriptResults -ScriptName “log4j-core files” -SiteCode “P..” -SiteServer “SCCM..”
    This is the warning message:
    WARNING: No Script found with the name log4j-core files in the ConfigMgr Script Repository
    I replaced the SiteCode and SiteServer with our own settings.

Leave a Reply