local-log4j-vuln-scanner VS log4jscanwin

The last scanner type is looking for the classes. Carnegie Mellon’s CERTCC released one that is referenced by CISA: https://github.com/CERTCC/CVE-2021-44228_scanner that look for class names and some fingerprints. Then there is a scanner written in Go that checks for the vulnerable class files and their hashes (inside JARs, WARs,EARs, and zips). https://github.com/hillu/local-log4j-vuln-scanner

I have been scanning with https://github.com/hillu/local-log4j-vuln-scanner and that problem was resolved in there.

If you want to scan your system for vulnerable log4j instances, https://github.com/hillu/local-log4j-vuln-scanner has binaries and is constantly updated

We are using this local log4j scanner: https://github.com/hillu/local-log4j-vuln-scanner/

https://github.com/hillu/local-log4j-vuln-scanner - Nope

Log4j may be included in other jars, so a recursive ps scan like https://github.com/hillu/local-log4j-vuln-scanner may come to rescue

The scanner provided by https://github.com/hillu/local-log4j-vuln-scanner gives us the following output when using "/opt/qradar/" as directory.

We're using Qualys free tool https://github.com/Qualys/log4jscanwin and it has a quite detailed output, and as far as I can tell it can also be read from Qualys cloud agent (we don't have it so I don't know how effective it is)

Here's the link to the stand-alone scanner: GitHub - Qualys/log4jscanwin: Log4j Vulnerability Scanner for Windows Very much worth having.

This just came out - haven’t tested it yet though - https://github.com/Qualys/log4jscanwin