NetSPI / PESecurity

PowerShell module to check if a Windows binary (EXE/DLL) has been compiled with ASLR, DEP, SafeSEH, StrongNaming, and Authenticode.

https://blog.netspi.com/verifying-aslr-dep-and-safeseh-with-powershell/

NetSPI/PESecurity Issues

Powershell Core 7 support
Closed 2 years ago8
ASLR High Entropy
Closed 2 years ago8
Window exe's SafeSEH is always false no matter the linker option is set or not from VS2019
Closed 2 years ago1
InvalidOperation in windows 10
Closed 4 years ago1
System.OutOfMemoryException when checking an entire hard drive
Updated 4 years ago3
Add support for /GS option
Updated 4 years ago1
SafeSEH reporting "False" when it is not
Closed 4 years ago2
SafeSEH Result is unreliable
Closed 4 years ago3
CFG reported False for managed executables (.NET)
Closed 4 years ago1
Certain binaries cannot be scanned
Updated 6 years ago3
SafeSEH reported False for resource-only DLLs
Updated 6 years ago1
ASLR check should verify that the relocation table hasn't been stripped in EXE files
Closed 6 years ago4
File not found and then PowerShell crash when doing a recursive directory scan
Updated 6 years ago1
Is this also showing, if a authenticode is valid?
Updated 8 years ago4
Missing license file
Closed 9 years ago1
Trim problem
Closed 9 years ago1
Consider renaming to Verb-Noun format
Closed 10 years ago1
Incorrect SafeSEH Determination
Closed 10 years ago2