Log4JShell-Bytecode-Detector
Local Bytecode Scanner for the Log4JShell Vulnerability (CVE-2021-44228) (by CodeShield-Security)
Log4jAttackSurface
By YfryTchsGD
Log4JShell-Bytecode-Detector | Log4jAttackSurface | |
---|---|---|
4 | 40 | |
50 | 2,085 | |
- | - | |
0.0 | 0.0 | |
about 2 years ago | over 2 years ago | |
Java | ||
MIT 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.
Log4JShell-Bytecode-Detector
Posts with mentions or reviews of Log4JShell-Bytecode-Detector.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-16.
- If you are hunting for log4j vulns, and you are already considering nested .jars..
-
Log4JShell ByteCode Detector
To check if your jar file is affected by the critical CVE-2021-44228, we provide an open-source command line tool https://github.com/CodeShield-Security/Log4JShell-Bytecode-Detector. The tool scans the jar file and compares the classses against a set of pre-computed hashes of the vulnerable Log4j classes. Since our tool only uses the hash and fingerprints of bytecode classes, no source code needs to be available.
- Zero-Day RCE Vulnerability CVE-2021-44228 aka Log4Shell: What We Know So Far
-
RCE 0-day exploit found in log4j, a popular Java logging package
u/sanitybit My colleagues have written a detector for the vulnerability: https://github.com/CodeShield-Security/Log4JShell-Bytecode-Detector
Log4jAttackSurface
Posts with mentions or reviews of Log4jAttackSurface.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-25.
-
Understanding and Exploiting Log4J Vulnerability
Checkout this link for knowing Log4j impact on manufacturers https://github.com/YfryTchsGD/Log4jAttackSurface
-
Dominion Voting wins key decision in lawsuit against Fox News
Just look at the currently ongoing insanity that is the log4j exploit, and how one single exploit has lead to a generic attack that can impact tons of companies. Imagine if a state decided to use voting machines, and someone found this style of exploit in the system.
-
Sustainable Open Source Software
Last week (Dec 9th) a major vulnerability was discovered in an open source logging project for Java called log4j. The vulnerability called Log4Shell would allow anyone to remotely run arbitrary code if they sent a message in the right format to the server. This is one of the worst attacks your system can be susceptible to and if you are interested in the technical details of the problem, here is an overview. The attack surface of Log4Shell is staggering, Amazon, Apple, Google, and the Apache Server are affected; it can almost not get bigger than this. We will see the real fallout of Log4Shell in the next weeks and months as right now servers worldwide are being scanned and prodded for this vulnerability.
-
Vulnerability Advisory: Apache Log Binary (Log4J)
Companies should verify they are not running any exposed Log4j Java code. Here is a list of impacted 3rd party software for your reference. If you find a server at risk, there are three potential ways to fix it as follows.
-
Using discovery to find devices with log4j installed
Looking for vendors/software on known lists like https://github.com/YfryTchsGD/Log4jAttackSurface
-
Schutz vor Log4j-Lücke – was hilft jetzt und was eher nicht
Blender ist nicht betroffen, #42
-
3 billion devices run log4j... including blender
It does and was also affected by log4j.
-
PSA: if you're hosting any public facing services make sure they're not vulnerable to the 0-day log4j RCE.
Thanks, sure it isn't complete but it does contain some scary and surprising (at least when first reading, of course the really aren't) things like: https://github.com/YfryTchsGD/Log4jAttackSurface/blob/master/pages/UniFi.md
- My feeds are full with the Log4j vulnerability, but let’s think about it for a moment…
-
Security Vulnerability in Minecraft: Java Edition
Apparently there's proof Steam along with many others are vulnerable.
What are some alternatives?
When comparing Log4JShell-Bytecode-Detector and Log4jAttackSurface you can also consider the following projects:
semgrep-rules - Semgrep rules registry
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
apache-log4j-rce-poc
teku - Open-source Ethereum consensus client written in Java
apache-log4j-rce-poc
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
GDLauncher - GDLauncher is a simple, yet powerful Minecraft custom launcher with a strong focus on the user experience
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin
log4j_CVE-2021-44228_tester - Multithreaded log4j vulnerability scanner using only bash! Tests all JNDI protocols, HTTP GET/POST, and 84 headers. [Moved to: https://github.com/ssstonebraker/log4j-scan-turbo]
Log4JShell-Bytecode-Detector vs semgrep-rules
Log4jAttackSurface vs nimbus-eth2
Log4JShell-Bytecode-Detector vs apache-log4j-rce-poc
Log4jAttackSurface vs teku
Log4JShell-Bytecode-Detector vs apache-log4j-rce-poc
Log4jAttackSurface vs apache-log4j-rce-poc
Log4JShell-Bytecode-Detector vs Apache Log4j 2
Log4jAttackSurface vs GDLauncher
Log4JShell-Bytecode-Detector vs active-scan-plus-plus
Log4jAttackSurface vs Apache Log4j 2
Log4JShell-Bytecode-Detector vs log4j_CVE-2021-44228_tester
Log4jAttackSurface vs active-scan-plus-plus