nse-log4shell
Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (CVE-2021-44228) (by Diverto)
| nse-log4shell | incidentresponse | |
|---|---|---|
| 4 | 6 | |
| 349 | 24 | |
| 0.0% | - | |
| 0.0 | 0.0 | |
| over 2 years ago | about 1 year ago | |
| Lua | PowerShell | |
| MIT License | - |
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
incidentresponse
Posts with mentions or reviews of incidentresponse.
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?
Use https://github.com/sp4ir/incidentresponse/blob/main/Get-Log4shellVuln.ps1 to find any jars with the JNDI look up.
- Remote searching log4j [Windows]
- Is this Powershell script thorough for detecting the Log4J vulnerability?
- Nice Log4J Response Arcserve....
- Everybody thinks that they can do IT because they’ve used a computer as users
-
Log4j PDQ scan profile
For now, I've setup two different scanners in PDQ. One of the PDQ example, and one of another I found, and running both to be safe. Here is the 2nd one I'm using, I modified it though so it wasn't trying to write direct to the C drive, as that may fail (but it does have to go to a folder that exists). https://github.com/sp4ir/incidentresponse/blob/35a2faae8512884bcd753f0de3fa1adc6ec326ed/Get-Log4shellVuln.ps1
What are some alternatives?
When comparing nse-log4shell and incidentresponse you can also consider the following projects:
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
log4jscanwin - Log4j Vulnerability Scanner for Windows
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
PowerShellSnippets
log4shell-tool - Log4Shell Enumeration, Mitigation and Attack Detection Tool
PatchAgainstLog4Shell - This is for patching against Log4Shell in Windows via Powershell
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
nse-log4shell vs CVE-2021-44228-Scanner
incidentresponse vs log4jscanwin
nse-log4shell vs local-log4j-vuln-scanner
incidentresponse vs PowerShellSnippets
nse-log4shell vs log4jscanwin
incidentresponse vs log4shell-tool
nse-log4shell vs PatchAgainstLog4Shell
incidentresponse vs local-log4j-vuln-scanner
incidentresponse vs CVE-2021-44228-Scanner
incidentresponse vs PatchAgainstLog4Shell
incidentresponse vs CVE-2021-44228-Log4Shell-Hashes