August 14, 2007
Microsoft Windows Media Player is prone to a remote code-execution vulnerability when handling specially crafted compressed skin files. Attackers exploit this issue by coercing unsuspecting users to download and open Windows Media Player skin files (WMZ or WMD files). Successful exploits allow attackers to execute arbitrary code in the context of the vulnerable application. This facilitates the remote compromise of affected computers.
- Avaya CIE 1.0
- Avaya CIE 1.0.2
- Avaya Customer Interaction Express (CIE) Server 1.0
- Avaya Customer Interaction Express (CIE) User Interface 1.0
- Avaya Customer Interaction Express (CIE) User Interface 1.0.2
- Microsoft Windows Media Player 10.0
- Microsoft Windows Media Player 11
- Microsoft Windows Media Player 7.1
- Microsoft Windows Media Player 9.0
Run all software as a nonprivileged user with minimal access rights.
To lessen the potential damage that successful exploits may achieve, run all software as a nonadministrative user with the least amount of privileges required to successfully operate.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from a successful exploit.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.
Microsoft has released an advisory along with fixes to address this issue. Please see the references for more information.
Piotr Bania, working with TippingPoint and the Zero Day Initiative, 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.