Microsoft issues stopgap fix for critical Windows flaw
'Fix It' for ailing shortcut vuln
Microsoft has published an automated workaround for the newly discovered Windows vulnerability that criminals are exploiting to seize control of computers, including some used to manage sensitive equipment at power plants and other industrial facilities.
The software giant began distributing the Fix It on Tuesday evening, five days after the vulnerability in every supported version of Windows became widely known. It automatically changes operating-system settings to protect users until a permanent patch is available. Previously, users had to make the changes manually, a process that risked bricking a PC in the event it wasn't carried out correctly.
Microsoft security response communications lead Christopher Budd warned that the workaround disables icon icons from being displayed as usual and recommended admins carefully test the fix before deploying it widely. Specifically, the change will cause folder and file icons on the task bar and start menu to be stripped of their graphical representations, making them appear as generic, white boxes. The Fix It will also require machines to be rebooted.
The stopgap measure comes as security researchers have found new ways to exploit the the critical vulnerability. Microsoft says it can be remotely triggered through the local network file-sharing features or the WebDAV, or Web Distributed Authoring and Versioning, client service. The open-source Metasploit framework for penetration testers has added a plug-in that remotely exploits the vulnerability, making it easy for black-hat hackers to target the bug as well. Previously, researchers said the vulnerability could be spread only by viewing the contents of an infected USB stick.
The vulnerability resides in the way Windows handles shortcut icons. The operating system fails to adequately parse some parameters, it's possible to embed malicious code in them that is automatically executed when an icon is viewed.
Criminals are actively exploiting the bug in targeted attacks, Microsoft and others have said. According to IDG News, at least one customer of SCADA, or supervisory control and data acquisition, software offered by Siemens has been hit by a computer worm that exploits the Windows flaw. The malware takes control of the systems, which are used to manage highly sensitive equipment at nuclear facilities, manufacturing plants and other industrial settings.
While the attacks seen to date have been highly targeted, security watchers warn they soon could become widespread. Microsoft hasn't said when it plans to offer a fix. The company's next patch release isn't scheduled until August 10, but officials haven't ruled out issuing an emergency fix ahead of that date. ®
The icon ** ISN'T ** designed to contain executable code, per se.
What's happening is that griefers and other miscreants have identified a flaw in the shortcut parsing mechanism that can be exploited by filling parameter fields within the shortcut with unexpected data.
These parameter fields are descriptors that are used to tell Windows what folder/file the shortcut points to, what application the target's MIME type is registered to, what image/bitmap to use to draw the shortcut's icon, things like that.
When the shortcut parser encounters this malformed data, instead of failing gracefully, the parser fails in such a way that causes the malformed data to be executed as machine code. This parameter-data-turned-machine-code can be used to do all sorts of nasty and/or unexpected things, depending on the privileges the code inherits from the parser, and/or the code's ability to break through the other layers of Windows' security subsystem.
This kind of attack can theoretically work on any OS with a modern, shortcut-and-icon-based GUI (including Linux and Mac OS X), ** IF ** the shortcut parser isn't up to snuff (in other words, is suffering from the same style of bug).
All you need to do is fill a *.desktop file (for a Linux desktop environment like GNOME or KDE) or resource fork (Mac OS X) with lots of specially-crafted extraneous data, and ** IF ** the GUI's shortcut / icon / *.desktop file / resource fork parser breaks in the right way, you ** MAY ** be able to exploit the situation to run arbitrary code.
Note that I am NOT saying that Linux or Mac OS X suffers from the same kind of hole. A lot of things need to fall into place in order to successfully exploit a weakness in any operating system component. I am speaking hypothetically, hence the prodigious use of the word ** IF **. No operating system is bullet-proof.
You said "beta testing", the presumes 2 things
1) There was alpha testing;
2) MS actually do any testing.
"Previously, users had to make the changes manually, a process that risked bricking a PC in the event it wasn't carried out correctly."
I hate to be a pedant and all, but that's not bricking. Bricking is a specific word meaning "to break beyond any hope of repair".Please don't misuse it, as it's a useful word.