CVE-2021-44228-Scanner
Apache Log4j 2
| CVE-2021-44228-Scanner | Apache Log4j 2 | |
|---|---|---|
| 17 | 108 | |
| 854 | 3,273 | |
| -0.1% | 0.4% | |
| 0.0 | 9.9 | |
| about 2 years ago | 2 days ago | |
| Java | Java | |
| Apache License 2.0 | 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
- find what log4j version windows server 2019 running
- Update latest bios legion 5 pro?
-
Detecting log4j on macos with Microsoft PowerShell
Take a look at https://github.com/logpresso/CVE-2021-44228-Scanner as another option
- Any free tool to scan for Log4Shell and Log4j vulnerabilities?
-
Help using command line scanner for Logj4 vulnerabilities
I found a scanner on Github that checks for Logj4 vulnerabilities that has versions for several different OSs including Linux but I am not familiar enough with Linux on Synology to run this on my own. I might figure it out if I spend a couple of hours but it would be really helpful to me, and I presume, others here if someone with the skills could respond with a short list of what to do to get this running, preferably as a one-time scheduled task or series of them if it takes that, rather than SSH'ing to the box.
- Horizon Client and log4j
-
So many different log4j scanner tools and scripts posted
Dell proposes Logpresso's log4j scan tool (https://github.com/logpresso/CVE-2021-44228-Scanner/releases) to mitigate vulnerabilities for various product lines, until they released actual fixes (various are still pending, so we only have the scan tool).
-
Well it's Log4J Patch Day. Again. (2.17 now available to fix infinite recursion bug)
Peculiarly Dell for some of their data protection products also seems to advice to use a 3rd party scan tool to mitigate against certain issues in <2.14 and 2.15 log4j using log4j-scan from Logpresso https://github.com/logpresso/CVE-2021-44228-Scanner, as far as I can see a Korean company? Would have imagined Dell would also have some developers being able to write something? But that's just me...
- So how exactly is Log4j supposed to be patched/mitigated on Windows?
- Detecting Log4j...
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.
apache-log4j-poc - Apache Log4j 远程代码执行
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
log4j-scanner - log4j-scanner is a project derived from other members of the open-source community by CISA to help organizations identify potentially vulnerable web services affected by the log4j vulnerabilities.
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
nse-log4shell - Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (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