| Info |
|---|
This article helps troubleshoot why the CVE-Check for Log4j crashes on Windows systems. |
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Problem
Together with a customer, we figured out a crash of the CVEthe CVE-2021-44228 -log4j 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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<<<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 Powershell script is returning returns only the incomplete output. That's why we need to execute the log4j2-scan.exe
...
| bgColor | #fff |
|---|
...
To solve this, you can use this manual:
...
...
...
en-us/windows/forum/all/vcruntime140dll-was-not-found/f43d5afd-9239-4913-8f32-20e44a959e13
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...