semgrep-rules
Log4JShell-Bytecode-Detector
| semgrep-rules | Log4JShell-Bytecode-Detector | |
|---|---|---|
| 8 | 4 | |
| 707 | 50 | |
| 1.0% | - | |
| 9.4 | 0.0 | |
| 1 day ago | about 2 years ago | |
| Solidity | Java | |
| GNU General Public License v3.0 or later | 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.
semgrep-rules
-
Powerful SAST project for Android Application Security
Nice and all, but why not contribute to https://github.com/returntocorp/semgrep-rules ?
-
Semgrep - Beta support for Rust
Well, the rules they actually added are pretty noisy. There's also not a lot of them.
-
Spring Actuator - Finding Actuators using Static Code Analysis - Part 2
The semgrep registry contains lots of rules for many issues, and you can contribute your own.
-
Just Say No To `:Latest`
Hadolint is great! If you want to customize your lint logic beyond the checks in it, I recently wrote a Semgrep rule to require all our Dockerfiles to pin images with a sha256 hash that could be a good starting point: https://github.com/returntocorp/semgrep-rules/pull/1861/file...
-
RCE 0-day exploit found in log4j, a popular Java logging package
Semgrep Rules for searching source code
-
Hacktoberfest and open-source security
Interested? More details are in this Hacktoberfest README.
- Semgrep rules registry: 1300 linter rules
Log4JShell-Bytecode-Detector
- 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
What are some alternatives?
find-sec-bugs - The SpotBugs plugin for security audits of Java web applications and Android applications. (Also work with Kotlin, Groovy and Scala projects)
apache-log4j-rce-poc
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
apache-log4j-rce-poc
ZAP - The ZAP core project
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
pyre-check - Performant type-checking for python.
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin
ThreatMapper - Open source cloud native security observability platform. Linux, K8s, AWS Fargate and more.
Log4jAttackSurface
hadolint - Dockerfile linter, validate inline bash, written in Haskell
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]