September 12, 2006
Microsoft Pragmatic General Multicast (PGM) is prone to a remote buffer-overflow vulnerability because the application fails to properly bounds-check externally supplied data. An attacker can exploit this issue to execute arbitrary code, facilitating a complete system compromise. This issue affects systems only when Microsoft Message Queuing (MSMQ) 3.0 is installed; this is not the default.
- HP Storage Management Appliance 2.1
- Microsoft Windows XP 64-bit Edition
- Microsoft Windows XP 64-bit Edition SP1
- Microsoft Windows XP 64-bit Edition Version 2003
- Microsoft Windows XP 64-bit Edition Version 2003 SP1
- Microsoft Windows XP
- Microsoft Windows XP Home
- Microsoft Windows XP Home SP1
- Microsoft Windows XP Home SP2
- Microsoft Windows XP Media Center Edition
- Microsoft Windows XP Media Center Edition SP1
- Microsoft Windows XP Media Center Edition SP2
- Microsoft Windows XP Professional
- Microsoft Windows XP Professional SP1
- Microsoft Windows XP Professional SP2
- Microsoft Windows XP Professional x64 Edition
- Microsoft Windows XP Tablet PC Edition
- Microsoft Windows XP Tablet PC Edition SP1
- Microsoft Windows XP Tablet PC Edition SP2
Block external access at the network boundary, unless external parties require service.
Block access at the perimeter to all computers that are not intended to be publicly accessible. This may limit exposure to remote attacks that exploit this vulnerability.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor all network traffic for signs of anomalous activity. This could include unexpected outgoing network traffic.
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 exploits of memory-corruption vulnerabilities.
Microsoft has released a security bulletin to address this issue. Please refer to the attached security bulletin for more information.
David Warden reported this issue to the vendor.
© 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 email@example.com.
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 firstname.lastname@example.org 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.