PatchAgainstLog4Shell
This is for patching against Log4Shell in Windows via Powershell (by SkeletonMan03)
incidentresponse | PatchAgainstLog4Shell | |
---|---|---|
6 | 2 | |
24 | 7 | |
- | - | |
0.0 | 0.0 | |
about 1 year ago | over 2 years ago | |
PowerShell | PowerShell | |
- | GNU General Public License v3.0 only |
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.
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
PatchAgainstLog4Shell
Posts with mentions or reviews of PatchAgainstLog4Shell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-18.
-
Log4j in tough to see places?
Powershell maybe? https://github.com/SkeletonMan03/PatchAgainstLog4Shell
-
So how exactly is Log4j supposed to be patched/mitigated on Windows?
I published a Powershell script to make finding and patching against Log4Shell easier on Windows systems. I hope it can help you, OP. Patch Against Log4Shell
What are some alternatives?
When comparing incidentresponse and PatchAgainstLog4Shell you can also consider the following projects:
log4jscanwin - Log4j Vulnerability Scanner for Windows
nse-log4shell - Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (CVE-2021-44228)
PowerShellSnippets
log4shell-tool - Log4Shell Enumeration, Mitigation and Attack Detection Tool
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
incidentresponse vs log4jscanwin
PatchAgainstLog4Shell vs nse-log4shell
incidentresponse vs PowerShellSnippets
PatchAgainstLog4Shell vs log4jscanwin
incidentresponse vs nse-log4shell
incidentresponse vs log4shell-tool
incidentresponse vs local-log4j-vuln-scanner
incidentresponse vs CVE-2021-44228-Scanner
incidentresponse vs CVE-2021-44228-Log4Shell-Hashes