MS kernel patch skirts infected machines
Damage control bypasses pwned PCs
Microsoft's latest batch of patches contains a kernel update designed not to install on machines infected with a rootkit.
The move is designed to prevent the confusion that occurred when one of the patches released in February resulted in a Blue Screen of Death and continuous reboot cycles on some Windows XP machines.
Microsoft copped a fair bit of criticism for the incident before the cause was pinned down to the interaction between the hard-to-detect Tdss rootkit and a Windows kernel security update. Rootkits are a type of malware that attempt to avoid detection by anti-virus scanners by burying themselves in the likes of Windows kernel code.
Redmond's April patch batch also contains a Windows kernel patch. In an effort to prevent the same snafu as February, Microsoft is using technology designed to prevent the update from installing onto malware-compromised machines.
"This security update includes package-detection logic that prevents the installation of the security update if certain abnormal conditions exist" Microsoft explains in the FAQ for its MS10-21 patch.
"These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update."
The same technology was used in a modified version of the MS10-15 update, which was initially released as part of February's Patch Tuesday and revised with an "avoid infected systems" add-on in mid-March.
Users who attempt to install either the revised MS010-15 package or the new Ms10-021 kernel update on infected machines ought to get an error code.
Possible error codes (such as 0x8007F0F4) fail to explain what might have gone wrong, but a bit of judicious searching ought to direct sys admins or regular users who hit the snag to this advisory here. This notice explains that users who run across problems installing the patch are probably dealing with a malware-infected machine.
Microsoft's April patch batch included 11 bulletins along with an update to the software giant's Malicious Software Removal Tool. The idea is that this tool will remove malware and clean up systems which can then by safely patched at the second time of asking. ®
"Microsoft is using technology designed to prevent the update from installing onto malware-compromised machines." because installing the patch may cause a BSOD
A bit like saying
"The fire brigade is using a new tool designed to prevent firefighters from spraying water at burning houses" because that might wet the sofa.
Really? If ever you needed proof that Microsoft aren't a serious software company....
This is just going to make things worse.
Consider scenarios A and B:
A. User with virus installs patch, bricks system, has to reinstall Windows, no longer has virus, was inconvenienced in the process but he's a Windows user so he's used to that sort of thing
B. User with virus attempts to install patch, thanks to MS gets weird error, ignores it, doesn't know they have virus, never gets patched, is insecure forever
And Microsoft prefers scenario B.
How about scenario D?
«User with virus attempts to install patch, thanks to MS gets the following incredibly clear message:
""Your computer might not be compatible with Microsoft Security Update MS10-015. Proceeding with installation of the update could prevent your system from starting successfully. For additional information please visit http://www.microsoft.com/security/updates/015." "»
User is used to getting strange error messages, can't be arsed to check the related URL (this minesweeper won't solve itself) and -as usual- just clicks OK and forgets about it. User never gets patched and is infected forever.