- Feb 22, 2007
- 16,240
- 7
- 76
ChiefCrowe posted in the security forum about this new malware. Originally it only targeted specific industrial systems so it wasn't much of a concern for most people.
http://forums.anandtech.com/showthread.php?t=2090206
Now it has been adapted by other malware creators and is going to spread like wildfire. I knew it would because when it was announced the boards where people request malware samples were going crazy with request for copies and most of them wanted it not for research but even saying they were going to use it to create, malware to steal information, generate spam, download malware, etc.
MS has no patch right now and is trying to get one out by Aug 10 but this is one that is going to be hard to patch because it is a feature in the core of the operating system. The MS fix for now is basically to disable icons completely since it needs the kernel to process the icon to run the malware.
MS patch to disable icons
http://support.microsoft.com/kb/2286198
http://isc.sans.edu/diary.html?storyid=9181
http://www.theregister.co.uk/2010/07/23/win_shortcut_vuln_goes_mainstream/
I know we have a security forum but I also know that most people do not read it and this one I think is serious enough that people really need to know it exist.
http://forums.anandtech.com/showthread.php?t=2090206
Now it has been adapted by other malware creators and is going to spread like wildfire. I knew it would because when it was announced the boards where people request malware samples were going crazy with request for copies and most of them wanted it not for research but even saying they were going to use it to create, malware to steal information, generate spam, download malware, etc.
MS has no patch right now and is trying to get one out by Aug 10 but this is one that is going to be hard to patch because it is a feature in the core of the operating system. The MS fix for now is basically to disable icons completely since it needs the kernel to process the icon to run the malware.
MS patch to disable icons
http://support.microsoft.com/kb/2286198
http://isc.sans.edu/diary.html?storyid=9181
The exploit uses a specially crafted LNK file. This file allows the attacker to execute an arbitrary file by carefully specifying its location the LNK file in itself does not exploit any vulnerability such as buffer overflows, for example, so it is a legitimate LNK file. The LNK file used in targeted attacks was manually crafted as some fields that are normally present, such as CreationTime, AccessTime or WriteTime are all set to 0.
The exploit is triggered every time a folder containing a malicious LNK files is opened (for example, with Windows Explorer). It does not matter where this folder is it does not have to be on a USB device, but in order to execute to malicious binary, the attacker has to specify its location correctly.
What makes this vulnerability extremely serious is the fact that it can be opened from any place, including remote shares, for example. The victim just has to browse to the remote share in order to trigger the vulnerability. So double check permissions on any remote shares you use in your companies (you shouldn't allow users to write in root folders, for example).
http://www.theregister.co.uk/2010/07/23/win_shortcut_vuln_goes_mainstream/
Virus writers have begun using the unpatched shortcut flaw in Windows first exploited by the Stuxnet worm, which targets power plant control systems, to create malware that infects the general population of vulnerable Windows machines.
Slovakian security firm Eset reports the appearance of two malware strains that exploit security vulnerabilities in the way Windows handles .lnk (shortcut) files, first used by Stuxnet to swipe information from Windows-based SCADA systems from Siemens.
The Chymine-A Trojan uses the same security hole to install a keystroke logger while the Autorun-VB-RP worm has been updated to use the shortcut vulnerability as an infection method. The original hackers developed a technique to embed malicious code in shortcut files in such a way that this code is run when an icon is viewed, an approach now followed by less skilled VXers.
Stuxnet featured rootlet functionality and digitally signed malware, techniques that mark it out as highly sophisticated. The latest malware to use the shortcut vulnerability is, by contrast, much more basic.
"The new malware we're seeing is far less sophisticated, and suggests bottom feeders seizing on techniques developed by others," writes Pierre-Marc Bureau, a senior researcher at Eset, in a blog post.
The shortcut vulnerability is likely to become a mainstay of malware distribution techniques, Bureau warns.
"This new development follows a typical path of evolution in malware. Often there are only days between the initial release of information regarding a critical vulnerability, and the discovery of its exploitation being executed in the wild by malware authors. It is safe to assume that more malware operators will start using this exploit code in order to infect host systems and increase their revenues," he concludes.
Trend Micro warns that the hole can be exploited by a wide variety of techniques including network shares, malicious websites and booby-trapped Office documents, as well as USB drive infection, the technique associated with the Stuxnet worm.
"File formats that support embedded shortcuts (eg Microsoft Office documents) can now be used to spread exploits as well," writes Trend Micro threat researcher David Sancho. "This means that users who download and open such files could find themselves the latest victim of this vulnerability. It has also been reported that this attack could be used in drive-by attack scenarios, further increasing risks."
Microsoft has issued temporary workarounds and security advice to customers as a stop-gap measure while its security researchers work on developing a fix. The vulnerability involves a security hole in core Windows functionality, so developing and testing a patch by the next scheduled Patch Tuesday, 10 August, will be tricky but not out of the question. Redmond's security team will have had a month by this point to go through a process that more typically takes two months or longer.
I know we have a security forum but I also know that most people do not read it and this one I think is serious enough that people really need to know it exist.
