local-log4j-vuln-scanner
CVE-2021-44228-Scanner
local-log4j-vuln-scanner | CVE-2021-44228-Scanner | |
---|---|---|
10 | 17 | |
381 | 854 | |
- | -0.1% | |
1.8 | 0.0 | |
almost 2 years ago | about 2 years ago | |
Go | Java | |
GNU General Public License v3.0 only | 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.
local-log4j-vuln-scanner
-
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
-
Log4jscanner by Google
I have been scanning with https://github.com/hillu/local-log4j-vuln-scanner and that problem was resolved in there.
-
So how exactly is Log4j supposed to be patched/mitigated on Windows?
If you want to scan your system for vulnerable log4j instances, https://github.com/hillu/local-log4j-vuln-scanner has binaries and is constantly updated
-
All log4j detection tools fail these cases - be careful
We are using this local log4j scanner: https://github.com/hillu/local-log4j-vuln-scanner/
-
Cisco AMP/Endpoint is not a great product for Endpoint Security.
https://github.com/hillu/local-log4j-vuln-scanner - Nope
- Vulnerabilidade Log4j
-
Can PDQ be used to scan for log4j usage?
Log4j may be included in other jars, so a recursive ps scan like https://github.com/hillu/local-log4j-vuln-scanner may come to rescue
-
Any mitigations in the works for the log4j critical CVE?
The scanner provided by https://github.com/hillu/local-log4j-vuln-scanner gives us the following output when using "/opt/qradar/" as directory.
- Log4j 0day being exploited
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...
What are some alternatives?
tfsec - Security scanner for your Terraform code
apache-log4j-poc - Apache Log4j 远程代码执行
log4jscanner - A log4j vulnerability filesystem scanner and Go package for analyzing JAR files.
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.
Log4jPatcher - A mitigation for CVE-2021-44228 (log4shell) that works by patching the vulnerability at runtime. (Works with any vulnerable java software, tested with java 6 and newer)
nse-log4shell - Nmap NSE scripts to check against log4shell or LogJam vulnerabilities (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
Windowslog4jClassRemover
Log4j-CVE-Detect - Detections for CVE-2021-44228 inside of nested binaries
LogCaptor - 🎯 LogCaptor captures log entries for unit and integration testing purposes