Windowslog4jClassRemover
apache-log4j-poc
Windowslog4jClassRemover | apache-log4j-poc | |
---|---|---|
3 | 3 | |
2 | 105 | |
- | - | |
3.2 | 3.8 | |
over 2 years ago | over 2 years ago | |
VBScript | Java | |
The Unlicense | - |
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.
Windowslog4jClassRemover
-
New Log4J CVE
Read the README and the Release Notes https://github.com/CrazyKidJack/Windowslog4jClassRemover/releases/latest
-
Mitigating log4j in Windows?
This is fine if you only have 1 or two JAR files to deal with and you don't mind installing 7-sip to do it. However, if you have lots of JAR files, or if you don't want to install 7-zip, I created an open-source VBS script that will do it for you without needing to install any additional software. https://github.com/CrazyKidJack/Windowslog4jClassRemover
-
Log4j 0day being exploited
While most people that need to know probably already know enough to do what they need to do AND the information from the OP is way more complete than mine, I have not seen anyone create a Windows script that can remove the JndiLookup.class file from log4j-core JARs easily the way the zip command is able to on linux. So I thought I would post this here if anyone needs to do that... https://github.com/CrazyKidJack/Windowslog4jClassRemover
apache-log4j-poc
-
2021-12-10 - Cool Query Friday - Hunting Apache Log4j CVE-2021-44228 (Log4Shell)
Proof of Concept
-
Log4j 0day being exploited
Exploit: https://github.com/tangxiaofeng7/apache-log4j-poc
-
Log4j RCE Found
Are there any mitigations in recent JVMs?
I tried reproducing this, and got the POC to hit the LDAP server, but it wouldn't load the test payload.
See also:
- https://github.com/tangxiaofeng7/apache-log4j-poc
What are some alternatives?
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
nuclei-templates - Community curated list of templates for the nuclei engine to find security vulnerabilities.
get-log4j-exploit-payload
rogue-jndi - A malicious LDAP server for JNDI injection attacks
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/
log4shell_ioc_ips - log4j / log4shell IoCs from multiple sources put together in one big file (IPs) more coming soon (CVE-2021-44228)
log4shelldetect - Rapidly scan filesystems for Java programs potentially vulnerable to Log4Shell (CVE-2021-44228) or "that Log4j JNDI exploit" by inspecting the class paths inside files
Log4j-CVE-Detect - Detections for CVE-2021-44228 inside of nested binaries
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions