-
Notifications
You must be signed in to change notification settings - Fork 1k
Fully Patched Box - Still showing KB's Applying #17
Comments
What you're describing sounds like there are unlinked KBs in the database. I've noticed some missing KBs in the XLS file that can raise false-positives, where the KB number is noted on the Microsoft website but is not present in the Excel sheet. If you'd like send me your redacted data and I can take a look and try and figure out where the problem lies. I think I may need to hardcode some specific KBs. |
Just hardcoded MS11-011. If anyone finds any more let me know. |
IRT wintermute4316's comments from Sept 28, 2016, I have noticed that, in Windows 7, systeminfo may not list all of the hotfixes installed on the machine (might be a limitation of the array). It will show a total of over 400 hotfixes applied, but only list the first 245 hotfixes by number. In order to get a complete list, you can type from the command line: wmic qfe get hotfixid Or, to run remotely: wmic /node:'computer name' get hotfixid Using the output from the above command yields identical results to a systeminfo run on Windows 10 (which has a complete hotfix list) as long as the -o option is used to specify the OS version (e.g. -o "Windows 10 Pro 64-bit"). Alternatively, by replacing the list of hotfixes in the original systeminfo file with the complete hotfix list from wmic qfe get hotfixid, you can skip the -o option. |
In reviewing the output from a scan of a Windows 10 Pro x64 v1607 (Build14393), the output from Windows-Exploit-Suggester gives a number of false positives in that it lists exploits that only apply to earlier Windows 10 builds. This might be solved by adding a function to exclude certain KBs based on Build #, since newer builds have all older patches incorporated (similar to a service pack). https://technet.microsoft.com/en-us/windows/release-info.aspx Below is the sanitized systeminfo and the resultant output. systeminfo: Windows-Exploit-Suggester: |
This may not apply to windows-exploit-suggester, but I tested this process on a fully patched Windows 7 desktop (ie. WindowsUpdate reports no patches needed and there are no pending reboots) however windows-exploit-suggester was still reporting KB's that were missing and possibly exploitable. When I tried to download and install those specific KB's manually from MS, following the links take you to another KB download and the installer would report that it's already installed. Is it possible that some of the missing KB#'s may not apply or are covered/superseded by other KB's? Could this be an issue with systeminfo, the MS database, and/or windows-exploit-suggester and the way it reports KB's?
Just trying to account for the inaccuracy and if it can be compensated for in windows-exploit-suggester.
The text was updated successfully, but these errors were encountered: