Windowslog4jClassRemover
Apache Log4j 2
| Windowslog4jClassRemover | Apache Log4j 2 | |
|---|---|---|
| 3 | 108 | |
| 2 | 3,268 | |
| - | 0.3% | |
| 3.2 | 9.9 | |
| over 2 years ago | 7 days ago | |
| VBScript | Java | |
| The Unlicense | Apache License 2.0 |
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 2
-
Hackers exploited Windows 0-day for 6 months after Microsoft knew of it
I don't think that's a good example. While Apache devs are volunteers and Microsoft devs are employees, they were criticized for their slow response time and seeming lack of urgency until it was far too late.
https://github.com/apache/logging-log4j2/pull/608#issuecomme...
- Create an alternative async logger implementation using JCTools
- Log4j requesting feedback on which modules/features to drop
- The Unsung Heroes of Open Source: The Dedicated Maintainers Behind Lesser-Known Projects
-
Studying Log4Shell
The official website. The vulnerability was introduced in 2.0-beta7 which was released in 2013.
-
The Dedicated Maintainers Behind Lesser-Known Open Source Projects
However, there are many open source projects that are widely used but not well-known, including cURL, ImageMagick, MyCLI, Homebrew, Apache Log4j, and OpenSSL. This article will take a closer look at these unsung heroes of the open source world. I do not want to give them a business model or financial advice in this article. This largely depends on the author's personal experience and values. I just want to raise more awareness about these open source projects.
-
Apache POI Setup Logging Error
What you need is log4j-core, what you downloaded is some kind of connector between log4j and JUL. Tbh I don't know what JUL is, but that's not important. You can get log4j-core on from the official website - https://logging.apache.org/log4j/2.x/ or in maven repo. In case you're not using maven, I highly, highly recommend you using it for managing your dependencies.
-
Log4Shell Still Has Sting in the Tail
> When it was first revealed in early December 2021, the Log4Shell bug was described as one of the most severe security vulnerabilities ever.
> The Apache Software Foundation, which maintains the open-source tool, quickly released a patch...
Apache horribly mismanaged this and did not release a patch until it was already widely known and being exploited in the wild. They also messed up and had to release several subsequent patches to actually fix the vulnerability.
Remember: this vulnerability was disclosed to them in November.
https://github.com/apache/logging-log4j2/pull/608#issuecomme...
-
The US Cybersecurity and Infrastructure Agency open-sourced a new tool named Scuba
Think back to the Log4J event, were you affected? (https://github.com/apache/logging-log4j2)
- In One Minute : log4j2
What are some alternatives?
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
Logback - The reliable, generic, fast and flexible logging framework for Java.
get-log4j-exploit-payload
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
log4shell_ioc_ips - log4j / log4shell IoCs from multiple sources put together in one big file (IPs) more coming soon (CVE-2021-44228)
Logstash - Logstash - transport and process your logs, events, or other data
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
SLF4J - Simple Logging Facade for Java
Log4j-CVE-Detect - Detections for CVE-2021-44228 inside of nested binaries
kibana - Your window into the Elastic Stack