Log4j-RCE-Scanner
log4j-scan
| Log4j-RCE-Scanner | log4j-scan | |
|---|---|---|
| 1 | 20 | |
| 255 | 3,333 | |
| - | 0.0% | |
| 3.8 | 0.0 | |
| 9 months ago | over 1 year ago | |
| Shell | Python | |
| GNU General Public License v3.0 only | MIT License |
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.
Log4j-RCE-Scanner
log4j-scan
-
Sublime Music - A FLOSS desktop client for Subsonic API servers (Airsonic, Navidrome, Gonic, etc)
Testing the image with github.com/fullhunt/log4j-scan and https://github.com/quay/clair shows no vulnerabilities
-
Finding the "practical" component for my thesis on Log4Shell
https://github.com/cisagov/log4j-scanner https://github.com/fullhunt/log4j-scan https://github.com/portswigger/log4shell-scanner
- Here's a log4j-scan in case you want to find vulnerable hosts in the pool of servers you own
-
Log4j2 nightmares for self hosters?
https://github.com/fullhunt/log4j-scan Used this one for my network. Worked just fine and no setup required to run on my host.
-
How to Check if a Java Project Depends on A Vulnerable Version of Log4j
The team at FullHunt provided an open-source tool called log4j-scan, an automated and extensive scanner for finding vulnerable Log4j hosts. It allows teams to scan their infrastructure but also test for WAF (Web Application Firewall) bypasses that can result in code execution. The tool has several options but in short, you pass to the tool the URL to scan and you get a report on the vulnerabilities found. For example:
-
Log4j for Dummies: How to Determine if Your Server (or Docker Container) Is Affected by the Log4Shell Vulnerability
Yep. Seems like https://github.com/fullhunt/log4j-scan/issues/80 would fix my issue. Thanks for the assist.
- A fully automated, accurate, and extensive scanner for finding log4j RCE CVE-2021-44228
- fullhunt/log4j-scan: A fully automated, accurate, and extensive scanner for finding log4j RCE CVE-2021-44228
- Log4j Vulnerability Cheatsheet
What are some alternatives?
log4jpwn - log4j rce test environment and poc
LogMePwn - A fully automated, reliable, super-fast, mass scanning and validation toolkit for the Log4J RCE CVE-2021-44228 vulnerability.
canarytokens - Canarytokens helps track activity and actions on your network.
log4j-scan-turbo - Multithreaded log4j vulnerability scanner using only bash! Tests all JNDI protocols, HTTP GET/POST, and 84 headers.
log4jscanner - A log4j vulnerability filesystem scanner and Go package for analyzing JAR files.
log4shell-vulnerable-app - Spring Boot web application vulnerable to Log4Shell (CVE-2021-44228).
mariadb-docker - Docker Official Image packaging for MariaDB
log4j2-rce-poc - A bare minimum proof-of-concept for Log4j2 JNDI RCE vulnerability (CVE-2021-44228/Log4Shell).
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/
log4jScanner - log4jScanner provides the ability to scan internal subnets for vulnerable log4j web services