CVE-2021-44228_scanner
Apache Log4j 2
CVE-2021-44228_scanner | Apache Log4j 2 | |
---|---|---|
13 | 108 | |
346 | 3,278 | |
0.0% | 0.5% | |
1.8 | 9.9 | |
about 2 years ago | about 4 hours ago | |
PowerShell | Java | |
BSD 2-clause "Simplified" 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.
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?
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?
hotpatch-for-apache-log4j2 - An agent to hotpatch the log4j RCE from CVE-2021-44228.
Logback - The reliable, generic, fast and flexible logging framework for Java.
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
nuclei - Fast and customizable vulnerability scanner based on simple YAML based DSL.
Logstash - Logstash - transport and process your logs, events, or other data
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
SLF4J - Simple Logging Facade for Java
log4shell - Operational information regarding the log4shell vulnerabilities in the Log4j logging library.
kibana - Your window into the Elastic Stack