Security Advisory

Microsoft Security Advisory 2896666

Vulnerability in Microsoft Graphics Component Could Allow Remote Code Execution

Published: November 05, 2013 | Updated: December 10, 2013

Version: 2.0

General Information

Executive Summary

Microsoft has completed the investigation into a private report of this vulnerability. We have issued MS13-096 to address the Microsoft Graphics Component Memory Corruption Vulnerability (CVE-2013-3906). For more information about this issue, including download links for an available security update, please review MS13-096.

Other Information


Microsoft thanks the following for working with us to help protect customers:

  • Haifei Li of McAfee Labs IPS Team for reporting the Microsoft Graphics Component Memory Corruption Vulnerability (CVE-2013-3906)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.




The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.


  • V1.0 (November 5, 2013): Advisory published.
  • V1.1 (November 12, 2013): Clarified the scope of the active attacks, clarified affected software configurations, and revised workarounds. These are informational changes only. Customers should re-evaluate the applicability of the suggested actions for their environments based on the updated information.
  • V2.0 (December 10, 2013): Advisory updated to reflect publication of security bulletin.

Built at 2014-04-18T13:49:36Z-07:00