apache-log4j-poc
CVE-2021-44228-Log4Shell-Hashes
apache-log4j-poc | CVE-2021-44228-Log4Shell-Hashes | |
---|---|---|
3 | 11 | |
105 | 153 | |
- | - | |
3.8 | 0.0 | |
over 2 years ago | over 2 years ago | |
Java | ||
- | - |
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.
apache-log4j-poc
-
2021-12-10 - Cool Query Friday - Hunting Apache Log4j CVE-2021-44228 (Log4Shell)
Proof of Concept
-
Log4j 0day being exploited
Exploit: https://github.com/tangxiaofeng7/apache-log4j-poc
-
Log4j RCE Found
Are there any mitigations in recent JVMs?
I tried reproducing this, and got the POC to hit the LDAP server, but it wouldn't load the test payload.
See also:
- https://github.com/tangxiaofeng7/apache-log4j-poc
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?
nuclei-templates - Community curated list of templates for the nuclei engine to find security vulnerabilities.
semgrep-rules - Semgrep rules registry
rogue-jndi - A malicious LDAP server for JNDI injection attacks
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
log4shell_ioc_ips - log4j / log4shell IoCs from multiple sources put together in one big file (IPs) more coming soon (CVE-2021-44228)
CVE-2021-44228_scanner - Scanners for Jar files that may be vulnerable to CVE-2021-44228
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin
jdk8u - https://wiki.openjdk.org/display/jdk8u
apache-log4j-rce-poc