log4shell
Operational information regarding the log4shell vulnerabilities in the Log4j logging library. (by NCSC-NL)
CVE-2021-44228_scanner
Scanners for Jar files that may be vulnerable to CVE-2021-44228 (by CERTCC)
| log4shell | CVE-2021-44228_scanner | |
|---|---|---|
| 41 | 13 | |
| 1,876 | 346 | |
| - | 0.0% | |
| 9.9 | 1.8 | |
| almost 2 years ago | about 2 years ago | |
| Python | PowerShell | |
| - | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of log4shell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-17.
-
Wetsvoorstel om cyberdreigingsinformatie breder te delen naar Tweede Kamer | Netherlands proposes law change to allow it's NCSC to share information more widely - Bill to share cyber threat information more broadly to the House of Representatives
I hope more organizations and governments do this. They had an excellent resource for Log4J. https://github.com/NCSC-NL/log4shell
- Are older OSs (specifically Mojave) extremely vulnerable to log4j, since they are no longer being patched?
-
Western Digital warns owners of My Cloud hard drives to update immediately
A few
- Log4j2 and consumer routers
-
Log4j UPDATE: 2.16 has a 7.5 DoS, 2.17 released
Nice list - https://github.com/NCSC-NL/log4shell/blob/main/software/README.md
-
Log4J – A 10 step mitigation plan
There are various tools, nicely again enumerated by NCSC-NL at their Github repository with which you can detect whether you are vulnerable. See which one you like best given the situation you are in.
Check what other software you are running and see if the software is vulnerable according to the list published by the NCSC-NL. CISA.gov has a similar registry.
-
I'm the closest thing to a system administrator at my company, and I don't know anything... what do I do about log4j, if anything?
There are multiple lists of software, the one I use is by the Dutch Cyber Security Center: https://github.com/NCSC-NL/log4shell/tree/main/software Everyday I cross reference on new changes and see if it effects my list. The list can be quite extensive and you might miss the most obvious ones like you FW, switches, SAN or some print software.
-
Log4J - Have your customer been breached? What have you seen if anything?
NCSC-NL has a researched list of specific vulnerabilities.
- GLPI IS NOT affected by the Log4j vulnerability CVE-2021-44228
CVE-2021-44228_scanner
Posts with mentions or reviews of CVE-2021-44228_scanner.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-16.
- 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?
What are some alternatives?
When comparing log4shell and CVE-2021-44228_scanner you can also consider the following projects:
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
hotpatch-for-apache-log4j2 - An agent to hotpatch the log4j RCE from CVE-2021-44228.
interactsh - An OOB interaction gathering server and client library
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
grype - A vulnerability scanner for container images and filesystems
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
glpi-agent - GLPI Agent
nuclei - Fast and customizable vulnerability scanner based on simple YAML based DSL.
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
SpongeForge - A Forge mod that implements SpongeAPI
log4shell-detector - Detector for Log4Shell exploitation attempts
log4shell vs Metabase
CVE-2021-44228_scanner vs hotpatch-for-apache-log4j2
log4shell vs interactsh
CVE-2021-44228_scanner vs CVE-2021-44228-Log4Shell-Hashes
log4shell vs grype
CVE-2021-44228_scanner vs Get-log4j-Windows.ps1
log4shell vs glpi-agent
CVE-2021-44228_scanner vs nuclei
log4shell vs syft
CVE-2021-44228_scanner vs local-log4j-vuln-scanner
log4shell vs SpongeForge
CVE-2021-44228_scanner vs log4shell-detector