log4shell
log4j2-rce-poc
log4shell | log4j2-rce-poc | |
---|---|---|
41 | 1 | |
1,876 | 3 | |
- | - | |
9.9 | 4.1 | |
almost 2 years ago | over 2 years ago | |
Python | Kotlin | |
- | - |
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.
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
log4j2-rce-poc
-
Log4J - Have your customer been breached? What have you seen if anything?
However, when using JNDI lookups, if you return properly formatted JNDI data (from a malicious server) then Java will execute that code. You can see this in PoC code: https://github.com/unlimitedsola/log4j2-rce-poc/blob/master/payload-server/src/main/kotlin/Main.kt
What are some alternatives?
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
Log4j-RCE-Scanner - Remote command execution vulnerability scanner for Log4j.
interactsh - An OOB interaction gathering server and client library
DogWalk-rce-poc - 🐾Dogwalk PoC (using diagcab file to obtain RCE on windows)
grype - A vulnerability scanner for container images and filesystems
fuelcms-rce - Fuel CMS 1.4 - Remote Code Execution
glpi-agent - GLPI Agent
CVE-2021-44228_scanner - Scanners for Jar files that may be vulnerable to CVE-2021-44228
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
SpongeForge - A Forge mod that implements SpongeAPI
GHSA-jfh8-c2jp-5v3q