nse-log4shell
Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (CVE-2021-44228) (by Diverto)
log4jscanwin
Log4j Vulnerability Scanner for Windows (by Qualys)
nse-log4shell | log4jscanwin | |
---|---|---|
4 | 4 | |
349 | 154 | |
0.0% | 0.0% | |
0.0 | 1.3 | |
over 2 years ago | about 1 year ago | |
Lua | C | |
MIT License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
nse-log4shell
Posts with mentions or reviews of nse-log4shell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-18.
-
So how exactly is Log4j supposed to be patched/mitigated on Windows?
log4shell or LogJam vulnerabilities (CVE-2021-44228) https://github.com/Diverto/nse-log4shell
-
What is the best way to perform vulnerability scans in a large organization?
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.
- I'm a fan of Cisco gear, but I can't justify moving forward. Their response to the log4j exploit has been awful and shows a lack of commitment to security.
- Our new tool for enumerating hidden Log4Shell-affected hosts
log4jscanwin
Posts with mentions or reviews of log4jscanwin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-16.
- log4j scanner for subnet
-
Log4 detection by enterprise tools
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)
-
Qualys Scans not finding Log4j, but Qualys stand-alone Log4j Vulnerability Scanner does?
Here's the link to the stand-alone scanner: GitHub - Qualys/log4jscanwin: Log4j Vulnerability Scanner for Windows Very much worth having.
-
So how exactly is Log4j supposed to be patched/mitigated on Windows?
This just came out - haven’t tested it yet though - https://github.com/Qualys/log4jscanwin
What are some alternatives?
When comparing nse-log4shell and log4jscanwin you can also consider the following projects:
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
incidentresponse
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
MacDirtyCow - Example of CVE-2022-46689 aka MacDirtyCow.
PatchAgainstLog4Shell - This is for patching against Log4Shell in Windows via Powershell
CVE-2022-22965 - 🚀 Exploit for Spring core RCE in C [ wip ]
nse-log4shell vs CVE-2021-44228-Scanner
log4jscanwin vs incidentresponse
nse-log4shell vs local-log4j-vuln-scanner
log4jscanwin vs CVE-2021-44228-Scanner
nse-log4shell vs incidentresponse
log4jscanwin vs MacDirtyCow
nse-log4shell vs PatchAgainstLog4Shell
log4jscanwin vs CVE-2022-22965
log4jscanwin vs local-log4j-vuln-scanner
log4jscanwin vs PatchAgainstLog4Shell