CVE-2021-44228_scanner
PowerShellSnippets
CVE-2021-44228_scanner | PowerShellSnippets | |
---|---|---|
13 | 8 | |
346 | 54 | |
0.0% | - | |
1.8 | 4.9 | |
about 2 years ago | over 2 years ago | |
PowerShell | PowerShell | |
BSD 2-clause "Simplified" 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.
CVE-2021-44228_scanner
- Bitcoin miner support/suggestions (log4j)
- Log4J Scanner via Ninja
- Log4 detection by enterprise tools
-
Log4J Network Scanning/Detection on a 100k+ Node Network
The last scanner type is looking for the classes. Carnegie Mellon’s CERTCC released one that is referenced by CISA: https://github.com/CERTCC/CVE-2021-44228_scanner that look for class names and some fingerprints. Then there is a scanner written in Go that checks for the vulnerable class files and their hashes (inside JARs, WARs,EARs, and zips). https://github.com/hillu/local-log4j-vuln-scanner
- Any free tool to scan for Log4Shell and Log4j vulnerabilities?
- Log4j vulnerability mitigation
-
Is Log4J really fixed?
See: https://github.com/CERTCC/CVE-2021-44228_scanner
-
Add CERTCC log4j scan to PDQ?
I'd like to use this to this script scan our network for log4j vulnberabilties: https://github.com/CERTCC/CVE-2021-44228_scanner
- Log4J "JndiLookup.class" question
- Is my Powershell Log4J scanner sufficient?
PowerShellSnippets
-
Script all database object to single file per object using dbatools
So if for whatever reason you can't get the dba tools to work (it looks like there is a viable answer above), you can always use scripting options with the script method to script out database objects, via SMO. I have a sample script here which is a bit different from what you've asked for, but shows the fundamentals of what you might want to do.
- Log4j vulnerability mitigation
-
In case anyone needs it, here's a quick and dirty powershell script to patch log4j to prevent log4shell (CVE-2021-44228)
Not that messy! I added a link to this thread and direct to the github link from my README on my scanner utility repo. When I get a chance I may borrow this and updated it to use the same remote methods I used in the last script, but read the file/computer list from my generated CSV - that way people can clean up the CSV for their particular targets, and push an update with this script. Nice work!
- The Log4j Vulnerability Explained : Detection and Exploitation | TryHackMe Log4j
-
Log4j PDQ scan profile
The issue with searching for log4j*.jar is that you miss out on bundled jars which have different filenames hashes. It might be a better approach to search for all jar files and look inside if there is a jndilookup.class mentioned. This might add some false positives - but this is imho better than false negatives. Here is a powershell script which implements that approach: https://github.com/omrsafetyo/PowerShellSnippets/blob/master/Invoke-Log4ShellScan.ps1
- Log4j 0day being exploited (mega thread/ overview)
- Log4Shell Scanner multi-server, massively parallel PowerShell
What are some alternatives?
hotpatch-for-apache-log4j2 - An agent to hotpatch the log4j RCE from CVE-2021-44228.
CVE-2021-44228-Log4Shell-Hashes - Hashes for vulnerable LOG4J versions
Logout4Shell - Use Log4Shell vulnerability to vaccinate a victim server against Log4Shell
Get-log4j-Windows.ps1 - Identifying all log4j components across all windows servers, entire domain, can be multi domain. CVE-2021-44228
Log4j-PoSH - Powershell tools for log4j vulnerability
nuclei - Fast and customizable vulnerability scanner based on simple YAML based DSL.
log4shell-tool - Log4Shell Enumeration, Mitigation and Attack Detection Tool
local-log4j-vuln-scanner - Simple local scanner for vulnerable log4j instances
incidentresponse
log4shell - Operational information regarding the log4shell vulnerabilities in the Log4j logging library.