log4shell-tools
Apache Log4j 2
Our great sponsors
log4shell-tools | Apache Log4j 2 | |
---|---|---|
8 | 108 | |
84 | 3,268 | |
- | 0.9% | |
4.5 | 9.9 | |
23 days ago | 5 days ago | |
Go | Java | |
MIT License | 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.
log4shell-tools
-
Log4j: The Pain Just Keeps Going and Going
I'm seeing this as well. While the amount of traffic has certainly decreased compared to the first couple of days after the CVE was announced, https://log4shell.tools is still being used by people every day.
-
How to send similar payload to different http headers?
e.g. from log4j. Taken from https://log4shell.tools/
-
Received a visit from the infamous Dejmnok420 today. Can anyone ELI5 the steps to take now?
I run tests with https://log4shell.tools, and it seems I'm vulnerable on client side, but my server is safe, which makes sense as I compiled the .jar 2 weeks ago with BuildTools as indicated here https://www.spigotmc.org/threads/spigot-security-releases-%E2%80%94-1-8-8%E2%80%931-18.537204/
-
Log4Shell Vulnerability Test Tool
You're right, but this has always been the trade off with tools like this. You put some trust in the tool's authors and gain some insight in return. Remember the services that tested for Heartbleed (e.g. https://filippo.io/Heartbleed/)? Fairly similar trade-off, but still these tools were widely used.
If you really don't trust me and have some technical know-how, you can self host the service. It's open source: https://github.com/alexbakker/log4shell-tools.
-
Log4j 2.15.0 – Previously suggested mitigations may not be enough
I can't say I'm feeling the same. Still lots of people testing over at https://log4shell.tools almost a week after this vulnerability became widely known. Plenty of people still discovering they're vulnerable as well. I think it's likely that these are just the people who know they're using log4j. If you're running a black box product from a vendor you'll have no clue you're vulnerable until it's too late.
-
Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
I have a feeling this vulnerability is going to be with us for years. Shameless plug: I built a tool that assists in detecting whether you're vulnerable to this or the previous CVE: https://log4shell.tools. Just enter the JNDI URI it gives you anywhere you suspect it ends up causing a message lookup in log4j. If log4j does so much as a DNS lookup, this tool will tell you about it.
-
log4shell.tools - Check if you're vulnerable to an egregious case of log4shell
Done! https://github.com/alexbakker/log4shell-tools
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?
ysoserial - A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
Logback - The reliable, generic, fast and flexible logging framework for Java.
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/
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
log4j-affected-db - A community sourced list of log4j-affected software
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
log4j2-without-jndi - log4j2-core JAR w/o JndiLookup.class
Logstash - Logstash - transport and process your logs, events, or other data
log4j-log4shell-affected - Lists of affected components and affected apps/vendors by CVE-2021-44228 (aka Log4shell or Log4j RCE). This list is meant as a resource for security responders to be able to find and address the vulnerability
SLF4J - Simple Logging Facade for Java
aegis4j - A Java agent that disables platform features you don't use, before an attacker uses them against you.
kibana - Your window into the Elastic Stack