I only know about CVE-2013-3900 (WinVerifyTrust) which allows modified files to pass signature check unless you tweak registry to enable patches.
I think there must be other instances like this where Microsoft won’t fix vulnerability or chooses insecure defaults, is there a list?
Of course, tons of tax dollars are spent hoarding vulns
Highly depends on your definitions of the words “vulnerabilities,” “Windows,” and “patched.” By Microsoft’s definitions of these words, the answer would be no.
Don’t know precisely, but hear from time to time that Microsoft is notorious for not patching in time in many cases, leaving vulnerabilities for months and sometimes years. I am pretty sure that MS just kinda gave up on the vulnerabilities MimiKatz exploits, so if the bad guys are on your network and you use MS infra it’s pretty much a question of time before they get admin credentials.
There are literally hundreds to thousands. Many of them are horded by governments, APTs, and pen testers. I personally abused a 10 year old CVE for pen tests that was known to be used by non US government entities for a zero click code execution on opening a word doc.
Then there are things that are vulnerabilities but cannot be fixed as they are intensic to how Windows functions. Some can be hardened from the defaults but break compatibility and some cannot be fixed without a complete rewrite of how Windows and AD work. Disa stigs will give you defaults that can be hardened. Requirements for all domain users to see all GPOs, users, groups in order for AD to work is an example of something that cannot be fixed without a complete rewrite. That means an in privileged user can get a list of all users, all domain administrator, names of all computers on the domain, etc. As an attacker, that is invaluable.
Short answer, that list is to big and changes constantly. None that would be comprehensive, but disa stigs is a good place to start.
