get-log4j-exploit-payload
By morphuslabs
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 (by 1lann)
get-log4j-exploit-payload | log4shelldetect | |
---|---|---|
1 | 3 | |
19 | 44 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | over 2 years ago | |
Java | Go | |
- | The Unlicense |
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.
get-log4j-exploit-payload
Posts with mentions or reviews of get-log4j-exploit-payload.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-09.
log4shelldetect
Posts with mentions or reviews of log4shelldetect.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-11.
-
Today is a bad day to run a VMWare cluster with thousands of java apps.
I'm not sure what you mean. You can deploy a built binary over your network and run it on all your servers. For example: curl -sSL https://github.com/1lann/log4shelldetect/releases/download/v0.0.2/log4shelldetect_0.0.2_Linux_x86_64.tar.gz | tar -C /tmp/ -zxf - log4shelldetect && /tmp/log4shelldetect -mode list /path/to/scan 2>/dev/null would download and extract the prebuilt binary to /tmp, and run it scanning at /path/to/scan, only outputting paths to potentially vulnerable .jars and ignoring warnings. You can replace the URL with your own build or distribute your own build as you wish.
- Log4j 0day being exploited
What are some alternatives?
When comparing get-log4j-exploit-payload and log4shelldetect you can also consider the following projects:
log4shell_ioc_ips - log4j / log4shell IoCs from multiple sources put together in one big file (IPs) more coming soon (CVE-2021-44228)
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
Windowslog4jClassRemover
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
CVE-2021-44228 - OpenIOC rules to facilitate hunting for indicators of compromise
log4j-sniffer - A tool that scans archives to check for vulnerable log4j versions
Log4j-CVE-Detect - Detections for CVE-2021-44228 inside of nested binaries
Empire - Empire is a PowerShell and Python post-exploitation agent.
get-log4j-exploit-payload vs log4shell_ioc_ips
log4shelldetect vs CVE-2021-44228-Scanner
get-log4j-exploit-payload vs Windowslog4jClassRemover
log4shelldetect vs local-log4j-vuln-scanner
get-log4j-exploit-payload vs CVE-2021-44228
log4shelldetect vs log4shell_ioc_ips
get-log4j-exploit-payload vs local-log4j-vuln-scanner
log4shelldetect vs log4j-sniffer
get-log4j-exploit-payload vs CVE-2021-44228-Scanner
log4shelldetect vs Log4j-CVE-Detect
log4shelldetect vs Windowslog4jClassRemover
log4shelldetect vs Empire