PrivescCheck icon indicating copy to clipboard operation
PrivescCheck copied to clipboard

Feature idea: whitelisted MSI packages auditing

Open garatc opened this issue 1 month ago • 5 comments

Hello,

I have worked on a PowerShell script that lists all installed MSI packages and cross-references them with the new SecureRepair whitelist introduced by Microsoft to revert specific MSI packages to their original, insecure pre-patch state where UAC is not showing during repair. My script shows whether the package is signed, writable and has any NoImpersonate custom action, which are common privesc paths.

I am thinking that it could be a good feature for your project? Either as it is now with the registry whitelist cross-reference or on all installed MSI packages by default, so it could also be used on older systems.

Link to my project: MSIAudit

Cheers!

garatc avatar Nov 04 '25 10:11 garatc

Hi!

This looks cool. I think it's a good idea indeed. I'll have to look more closely into it.

Thanks for the suggestion.

itm4n avatar Nov 04 '25 10:11 itm4n

That was quick!

Let me know if you want me to open a PR and implement it there directly.

garatc avatar Nov 04 '25 10:11 garatc

Thanks, no need to open a PR. I prefer to implement things myself as far as possible honestly. This way, I'm sure I understand all aspects, especially when it's a new feature. This goes without saying that I'll credit your work though.

itm4n avatar Nov 04 '25 11:11 itm4n

FYI, I simplified the script a bit (no need to check for signature in our case - probably only useful for MST backdoors) and added a parameter to just scan all packages regardless of the whitelist (useful for older systems that do not have this whitelist)

garatc avatar Nov 05 '25 13:11 garatc

Hello! I was wondering if you had any ETA regarding this (no pressure of course, just asking if you've already planned something). I still have clients running Windows 10 by the way, where vulnerable MSI packages are even easier to exploit!

garatc avatar Nov 28 '25 14:11 garatc