PESecurity icon indicating copy to clipboard operation
PESecurity copied to clipboard

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

Results 7 PESecurity issues
Sort by recently updated
recently updated
newest added

It seems reasonable to do a scan of the executable code on an entire system. To do this, I ran: Get-PESecurity -Directory 'C:\' -Recursive > pesecurity.log Eventually the script started...

Request to add support for stack protection (/GS) option - see https://msdn.microsoft.com/en-us/library/8dbf701c.aspx for more information

Hi Get-PESecurity is a great tool, and it works well to scan a wide variety of EXEs and DLLs...I have one EXE that fails to scan (hasplms.exe sentinel security license...

bug

SafeSEH is reported False for resource-only DLLs. While it is technically valid, it just generates a noise in the reports as this can't be 'fixed' in the DLL itself. Resource-only...

bug

It's not clear if this is related to Issue #13 or not, but on a Windows 7 system with PowerShell 4, I'm trying to do a recursive directory scan of...

Hey, first of all thanks for providing this. Can you tell me, if this is also providing information about the validity of a authenticode signing? Thanks in advance!

Adding ARM64 arch definition according to https://learn.microsoft.com/en-us/dotnet/api/system.reflection.portableexecutable.machine?view=net-8.0