Vulnerability Note VU#300549

Microsoft Windows Graphics Rendering Engine buffer overflow vulnerability

Original Release date: 08 Nov 2005 | Last revised: 08 Feb 2006


Microsoft Windows Graphics Rendering Engine contains a buffer overflow that may allow a remote attacker to execute arbitrary code on a vulnerable system.


The Microsoft Windows Graphics Rendering Engine supports a number of image formats including Windows Metafile (WMF) and Enhanced Metafile (EMF). The Windows Graphics Rendering Engine fails to properly validate WMF and EMF image files. This may allow a remote attacker to manipulate memory allocation routines to create an under-sized buffer. When data is copied to this buffer, a heap-based buffer overflow may occur.

Note that according to public reports, this vulnerability may also affect the Graphical Device Interface (GDI) subsystem.


By persuading a user to open a specially crafted WMF or EMF image file, an attacker may be able to execute arbitrary code with the privileges of the user.


Apply an update

Microsoft has addressed this issue in Microsoft Security Bulletin MS05-053.

Do not accept WMF or EMF files from untrusted sources

By only accessing WMF or EMF image files from trusted or known sources, the chances of exploitation are reduced.

For additional workarounds and mitigating factors for this vulnerability, please see MS05-053.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Microsoft CorporationAffected-08 Nov 2005
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



This vulnerability was reported in Microsoft Security Bulletin MS05-053. Microsoft credits eEye Digital Security and Symantec Security Response for

This document was written by Jeff Gennari.

Other Information

  • CVE IDs: CVE-2005-2123
  • Date Public: 08 Nov 2005
  • Date First Published: 08 Nov 2005
  • Date Last Updated: 08 Feb 2006
  • Severity Metric: 13.37
  • Document Revision: 15


If you have feedback, comments, or additional information about this vulnerability, please send us email.