local-log4j-vuln-scanner VS nse-log4shell

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.

log4shell or LogJam vulnerabilities (CVE-2021-44228) https://github.com/Diverto/nse-log4shell

Awesome! If you're worldwide, it may take some coordination on best time to patch them once discovered. Aside from Nessus, you could carefully do an nmap scan a couple subnets or location at a time.