Logout4Shell
log4shell
Logout4Shell | log4shell | |
---|---|---|
34 | 41 | |
1,727 | 1,876 | |
- | - | |
2.6 | 9.9 | |
over 2 years ago | almost 2 years ago | |
Java | Python | |
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.
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!
log4shell
-
Wetsvoorstel om cyberdreigingsinformatie breder te delen naar Tweede Kamer | Netherlands proposes law change to allow it's NCSC to share information more widely - Bill to share cyber threat information more broadly to the House of Representatives
I hope more organizations and governments do this. They had an excellent resource for Log4J. https://github.com/NCSC-NL/log4shell
- Are older OSs (specifically Mojave) extremely vulnerable to log4j, since they are no longer being patched?
-
Western Digital warns owners of My Cloud hard drives to update immediately
A few
- Log4j2 and consumer routers
-
Log4j UPDATE: 2.16 has a 7.5 DoS, 2.17 released
Nice list - https://github.com/NCSC-NL/log4shell/blob/main/software/README.md
-
Log4J – A 10 step mitigation plan
There are various tools, nicely again enumerated by NCSC-NL at their Github repository with which you can detect whether you are vulnerable. See which one you like best given the situation you are in.
Check what other software you are running and see if the software is vulnerable according to the list published by the NCSC-NL. CISA.gov has a similar registry.
-
I'm the closest thing to a system administrator at my company, and I don't know anything... what do I do about log4j, if anything?
There are multiple lists of software, the one I use is by the Dutch Cyber Security Center: https://github.com/NCSC-NL/log4shell/tree/main/software Everyday I cross reference on new changes and see if it effects my list. The list can be quite extensive and you might miss the most obvious ones like you FW, switches, SAN or some print software.
-
Log4J - Have your customer been breached? What have you seen if anything?
NCSC-NL has a researched list of specific vulnerabilities.
- GLPI IS NOT affected by the Log4j vulnerability CVE-2021-44228
What are some alternatives?
grype - A vulnerability scanner for container images and filesystems
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
airsonic-advanced
interactsh - An OOB interaction gathering server and client library
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
glpi-agent - GLPI Agent
Logout4Shell - Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
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
SpongeForge - A Forge mod that implements SpongeAPI