Microsoft Windows GDI WMF Handling Heap Overflow Vulnerability
6/13/2006 12:00:00 AM
The Microsoft Windows GDI Graphics Rendering Engine is prone to a heap-overflow vulnerability. This issue is exposed when the component loads a specially crafted WMF (Windows Metafile) image.
If this issue is exploited, a malicious WMF or EMF file could potentially corrupt heap-based memory with attacker-supplied data. This could lead to the execution of arbitrary code and to a complete system compromise.
An attacker could exploit the issue by enticing the victim user to visit a malicious web page that contains the image or to open an email attachment that consists of the image.
This vulnerability is limited to Windows 98/98SE/ME systems.
Microsoft Windows ME
Microsoft Windows 98
Microsoft Windows 98SE
Do not accept or execute files from untrusted or unknown sources.
Attackers may exploit this issue via malicious WMF images. Users are advised to avoid opening any unsolicited or unexpected email attachments.
Do not follow links provided by unknown or untrusted sources.
Attackers may exploit this issue via a malicious website. Users should be wary of visiting websites of questionable integrity, especially if solicited to do so by an untrusted or unfamiliar source.
Microsoft has released a security bulletin to address this issue. Fixes may be obtained through Windows Update.
Source: Microsoft Security Bulletin MS06-026
Discovery is credited to Peter Ferrie of Symantec.
Copyright © by Symantec Corp.
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.