This article helps troubleshoot why the CVE-Check for Log4j crashes on Windows systems.
LAST TESTED ON CHECKMK 2.0.0P1
Problem
Together with a customer, we figured out a crash of the CVE-2021-44228 Log4j Checkmk from the Checkmk Exchange Site: https://exchange.checkmk.com/p/cve-2021-44228-log4j
The problem seems to be the incomplete agent output:
<<<cve_2021_44228_log4j:sep(0):cached(1640096053,86400)>>> 2021-12-21T15:14:13+01:00 SCAN OPTIONS: --all-drives <<<>>>
Solution
Let's debug this further on the Windows machine:
The Powershell script returns only the incomplete output. That's why we need to execute the log4j2-scan.exe
To solve this, you can use this manual: https://answers.microsoft.com/en-us/windows/forum/all/vcruntime140dll-was-not-found/f43d5afd-9239-4913-8f32-20e44a959e13
Related articles