Microsoft Virtual PC and Virtual Server Heap Overflow Vulnerability



Date Discovered

August 14, 2007


Microsoft Virtual PC and Virtual Server are prone to a local heap-overflow vulnerability. To exploit this issue, attackers must have administrative privileges for the guest operating system. Attackers may exploit this issue to execute arbitrary code in the context of the host operating system or another guest operating system. Successful exploits can result in a compromise of vulnerable computers.

Technologies Affected

  • Microsoft Virtual PC 2004
  • Microsoft Virtual PC 2004 SP1
  • Microsoft Virtual PC for Mac 6.1
  • Microsoft Virtual PC for Mac 7
  • Microsoft Virtual Server 2005 Enterprise Edition
  • Microsoft Virtual Server 2005 Enterprise Edition R2
  • Microsoft Virtual Server 2005 Standard Edition
  • Microsoft Virtual Server 2005 Standard Edition R2


Permit privileged access for trusted individuals only.
Given the nature of this issue, permit administrative access to trusted individuals only.

Microsoft released security bulletin MS07-049 and fixes to address this issue. Update Nov 13, 2007: The vendor has released security bulletin MS07-049 stating that previous updates did not correctly install in certain situations. Users are advised to install the latest available updates. Please see the referenced bulletin for more information.



Rafal Wojtczuk of McAfee Avert Labs is credited with discovering this issue.

© 1995- 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


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 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.