December 28, 2005
Microsoft Windows WMF graphics rendering engine is affected by a remote code-execution vulnerability. This issue affects the 'SetAbortProc' function.
The problem presents itself when a user views a malicious WMF formatted file, triggering the vulnerability when the engine attempts to parse the file.
The issue may be exploited remotely or locally. Any remote code execution that occurs will be with the privileges of the user viewing a malicious image. An attacker may gain SYSTEM privileges if an administrator views the malicious file.
Local code execution may facilitate a complete compromise.
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Do not allow untrusted individuals to have local access to computers. This may limit exposure to local attack vectors.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor all network traffic for signs of suspicious or anomalous activity. This may aid in detecting attempts to exploit latent vulnerabilities or in detecting malicious activity that occurs as a result of successful exploitation.
Do not accept or execute files from untrusted or unknown sources.
Users should not accept files from untrusted or unknown sources as they may be malicious in nature.
Do not follow links provided by unknown or untrusted sources.
Always avoid websites of questionable integrity. Never follow links supplied by unknown or untrusted sources.
Do not accept communications that originate from unknown or untrusted sources.
Disabling client support for HTML email may limit exposure to this attack vector.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as non-executable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploitation of memory-corruption vulnerabilities.
Please see the referenced advisories for more information:
- Microsoft has released a security advisory (Microsoft Security Advisory (912840)) confirming this issue. The referenced advisory contains information about workarounds; the vendor plans to release updates in the near future.
- Microsoft has released a security advisory (Microsoft Security Bulletin MS06-001) to address this issue for supported operating systems. Reports indicate that users who have disabled Microsoft Windows Picture and Fax Viewer by deregistering 'shimgvw.dll' may have to register it manually after applying fixes released by Microsoft. Please see the Workaround section for instructions on registering 'shimgvw.dll'.
- Avaya has released advisory ASA-2006-001 to identify vulnerable Avaya products. Avaya recommends installing Microsoft fixes to address this issue on affected computers.
- Gentoo Linux has released advisory GLSA 200601-09 to address this issue in Wine. Users of affected packages should execute the following commands with superuser privileges:
emerge --ask --oneshot --verbose ">=app-emulation/wine-20050930"
- Nortel Networks has released a security advisory to address this issue in various products.
- Microsoft has released patches to address this issue in Microsoft Windows Vista Beta 1 and Windows Vista December CTP (Community Technology Preview). See fixes for the Windows Vista December CTP (Community Technology Preview) patch. Users are advised to contact Microsoft for the Windows Vista Beta 1 patch.
- Gentoo has released advisory GLSA 200601-09:02 to replace fixes that were released as part of the Gentoo advisory 200601-09. The fixes released in the previous advisory did not properly address this issue. Please see the referenced advisory for more information. All Wine users should re-emerge Wine by carrying out the following commands:
emerge --ask --oneshot --verbose ">=app-emulation/wine-0.9.0"
- Debian has released advisory DSA 954-1 to address this issue in Wine. Please see the referenced advisory for more information.
The individual responsible for discovering this issue not currently known.
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com
are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.