CVE-2021-44228_scanner
hotpatch-for-apache-log4j2
| CVE-2021-44228_scanner | hotpatch-for-apache-log4j2 | |
|---|---|---|
| 13 | 10 | |
| 346 | 497 | |
| 0.0% | 0.0% | |
| 1.8 | 0.0 | |
| about 2 years ago | over 1 year ago | |
| PowerShell | Java | |
| BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
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.
CVE-2021-44228_scanner
- Bitcoin miner support/suggestions (log4j)
- Log4J Scanner via Ninja
- Log4 detection by enterprise tools
-
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
- Any free tool to scan for Log4Shell and Log4j vulnerabilities?
- Log4j vulnerability mitigation
-
Is Log4J really fixed?
See: https://github.com/CERTCC/CVE-2021-44228_scanner
-
Add CERTCC log4j scan to PDQ?
I'd like to use this to this script scan our network for log4j vulnberabilties: https://github.com/CERTCC/CVE-2021-44228_scanner
- Log4J "JndiLookup.class" question
- Is my Powershell Log4J scanner sufficient?
hotpatch-for-apache-log4j2
- Log4j vulnerability mitigation
- Amazon Linux Hotpatch for Apache Log4j Needs a Patch
- AWS injected bad code into customer run Java web apps
- AWS’s Hotpatch Agent for Log4j
-
Log4Shell Remediation Cheat Sheet | Created by Java Champion and security researcher at Snyk
For mitigation, there is also the option of last resort of hotpatching the JVM that was posted here a couple times: https://github.com/corretto/hotpatch-for-apache-log4j2
- A JavaAgent based hotpatch for fixing live JVMs with the log4shell vulnerability
-
Hotpatch for Apache Log4j released
Source Code - https://github.com/corretto/hotpatch-for-apache-log4j2
- corretto/hotpatch-for-apache-log4j2: An agent to hotpatch the log4j RCE from CVE-2021-44228, no JVM restarts needed. Patching > hotpatching > nothing.
- A Java based hotpatch for the Log4Shell vulnerability (log4j2 CVE)
What are some alternatives?
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
hotpatch-for-apache-log4j2 - An agent to hotpatch the log4j RCE from CVE-2021-44228.
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
PowerShellSnippets
nuclei - Fast and customizable vulnerability scanner based on simple YAML based DSL.
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
log4shell - Operational information regarding the log4shell vulnerabilities in the Log4j logging library.
log4shell-detector - Detector for Log4Shell exploitation attempts
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
log4j2-rce-poc - A bare minimum proof-of-concept for Log4j2 JNDI RCE vulnerability (CVE-2021-44228/Log4Shell).