local-log4j-vuln-scanner
log4jshield
| local-log4j-vuln-scanner | log4jshield | |
|---|---|---|
| 10 | 2 | |
| 381 | 14 | |
| - | - | |
| 1.8 | 0.0 | |
| almost 2 years ago | over 2 years ago | |
| Go | Shell | |
| GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
local-log4j-vuln-scanner
-
Log4J Network Scanning/Detection on a 100k+ Node Network
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
-
Log4jscanner by Google
I have been scanning with https://github.com/hillu/local-log4j-vuln-scanner and that problem was resolved in there.
-
So how exactly is Log4j supposed to be patched/mitigated on Windows?
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
-
All log4j detection tools fail these cases - be careful
We are using this local log4j scanner: https://github.com/hillu/local-log4j-vuln-scanner/
-
Cisco AMP/Endpoint is not a great product for Endpoint Security.
https://github.com/hillu/local-log4j-vuln-scanner - Nope
- Vulnerabilidade Log4j
-
Can PDQ be used to scan for log4j usage?
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
-
Any mitigations in the works for the log4j critical CVE?
The scanner provided by https://github.com/hillu/local-log4j-vuln-scanner gives us the following output when using "/opt/qradar/" as directory.
- Log4j 0day being exploited
log4jshield
What are some alternatives?
tfsec - Security scanner for your Terraform code
log4j-scan-turbo - Multithreaded log4j vulnerability scanner using only bash! Tests all JNDI protocols, HTTP GET/POST, and 84 headers.
log4jscanner - A log4j vulnerability filesystem scanner and Go package for analyzing JAR files.
log4j-detector - A public open sourced tool. Log4J scanner that detects vulnerable Log4J versions (CVE-2021-44228, CVE-2021-45046, etc) on your file-system within any application. It is able to even find Log4J instances that are hidden several layers deep. Works on Linux, Windows, and Mac, and everywhere else Java runs, too! TAG_OS_TOOL, OWNER_KELLY, DC_PUBLIC
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
Log4j-RCE-Scanner - Remote command execution vulnerability scanner for Log4j.
Log4jPatcher - A mitigation for CVE-2021-44228 (log4shell) that works by patching the vulnerability at runtime. (Works with any vulnerable java software, tested with java 6 and newer)
log4shell_ioc_ips - log4j / log4shell IoCs from multiple sources put together in one big file (IPs) more coming soon (CVE-2021-44228)
nse-log4shell - Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (CVE-2021-44228)
Windowslog4jClassRemover
apache-log4j-poc - Apache Log4j 远程代码执行
Log4j-CVE-Detect - Detections for CVE-2021-44228 inside of nested binaries