Log4JShell-Bytecode-Detector
Local Bytecode Scanner for the Log4JShell Vulnerability (CVE-2021-44228) (by CodeShield-Security)
CVE-2021-44228-Log4Shell-Hashes
Hashes for vulnerable LOG4J versions (by mubix)
Log4JShell-Bytecode-Detector | CVE-2021-44228-Log4Shell-Hashes | |
---|---|---|
4 | 11 | |
50 | 153 | |
- | - | |
0.0 | 0.0 | |
about 2 years ago | over 2 years ago | |
Java | ||
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
Log4JShell-Bytecode-Detector
Posts with mentions or reviews of Log4JShell-Bytecode-Detector.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-16.
- If you are hunting for log4j vulns, and you are already considering nested .jars..
-
Log4JShell ByteCode Detector
To check if your jar file is affected by the critical CVE-2021-44228, we provide an open-source command line tool https://github.com/CodeShield-Security/Log4JShell-Bytecode-Detector. The tool scans the jar file and compares the classses against a set of pre-computed hashes of the vulnerable Log4j classes. Since our tool only uses the hash and fingerprints of bytecode classes, no source code needs to be available.
- Zero-Day RCE Vulnerability CVE-2021-44228 aka Log4Shell: What We Know So Far
-
RCE 0-day exploit found in log4j, a popular Java logging package
u/sanitybit My colleagues have written a detector for the vulnerability: https://github.com/CodeShield-Security/Log4JShell-Bytecode-Detector
CVE-2021-44228-Log4Shell-Hashes
Posts with mentions or reviews of CVE-2021-44228-Log4Shell-Hashes.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-16.
-
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?
When comparing Log4JShell-Bytecode-Detector and CVE-2021-44228-Log4Shell-Hashes you can also consider the following projects:
semgrep-rules - Semgrep rules registry
apache-log4j-rce-poc
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
apache-log4j-rce-poc
apache-log4j-poc - Apache Log4j 远程代码执行
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin
CVE-2021-44228_scanner - Scanners for Jar files that may be vulnerable to CVE-2021-44228
Log4jAttackSurface
Log4JShell-Bytecode-Detector vs semgrep-rules
CVE-2021-44228-Log4Shell-Hashes vs semgrep-rules
Log4JShell-Bytecode-Detector vs apache-log4j-rce-poc
CVE-2021-44228-Log4Shell-Hashes vs Get-log4j-Windows.ps1
Log4JShell-Bytecode-Detector vs apache-log4j-rce-poc
CVE-2021-44228-Log4Shell-Hashes vs apache-log4j-poc
Log4JShell-Bytecode-Detector vs Apache Log4j 2
CVE-2021-44228-Log4Shell-Hashes vs Apache Log4j 2
Log4JShell-Bytecode-Detector vs active-scan-plus-plus
CVE-2021-44228-Log4Shell-Hashes vs CVE-2021-44228_scanner
Log4JShell-Bytecode-Detector vs Log4jAttackSurface
CVE-2021-44228-Log4Shell-Hashes vs active-scan-plus-plus