I noticed this morning that one of my baselines is failing on some machines. The patch is fixlet ID 1205901 “MS12-059: Vulnerability in Microsoft Visio Could Allow Remote Code Execution - Microsoft Visio 2010 SP1 (KB2687508) (V2.0)”
On each computer, it fails with exit code 17025. According to Microsoft’s site, this means “Patch already installed”. So I guess the relevance is false positive.
MS12-059 hasn’t had problems up until now it seems, but maybe you’ve noticed some weird corner case. Can you open up a PMR so that we can follow up on this and track down what’s going on with those endpoints?
I think isolated the cause and have a fix for this, but we haven’t gotten confirmation that it works yet. I’ll post the fix here and you guys can tell me whether this seems to work or not…
If it works we’ll go ahead and roll this out into production. Thanks!
You want to treat it like a fixlet, where you evaluate the success or failure of an action based off of the overall relevance going from true to false (rather than just successfully executing all the commands in a given action).
Also, I think we finally got an update that the fixlet seems to do the right thing on the original bug so once we double check a few things this is going to be published.
I am not sure if this is resolved. What I am seeing is that the following two fixlets are having issues with relevance.
1205906 MS12-059: Vulnerability in Microsoft Visio Could Allow Remote Code Execution - Microsoft Visio 2010 SP1 (KB2687508) (x64) (V2.0) Important Patches for Windows (English) 0 / 16,225 0 Security Hotfix 17.12 MB Microsoft KB2687508 12/11/2012
1205901 MS12-059: Vulnerability in Microsoft Visio Could Allow Remote Code Execution - Microsoft Visio 2010 SP1 (KB2687508) (V2.0) Important Patches for Windows (English) 24 / 16,225 0 Security Hotfix 13.82 MB Microsoft KB2687508 12/11/2012
I am wondering if this is because these should have actually been marked as superceded like the other two fixlets for this MS#. When I look at the link: http://technet.microsoft.com/en-us/security/bulletin/MS13-023
is seems to indicate that MS13-023 also superceded the KB2687508 patch.