April 8, 2008
Microsoft VBScript and JScript are prone to a remote code-execution vulnerability because they fail to adequately handle user-supplied input. Attackers can leverage this issue by enticing an unsuspecting user to view a malicious web document. Successful exploits would allow arbitrary code to run with the privileges of the victim. These versions are affected: VBScript 5.6 and earlier JScript 5.6 and earlier
- HP Storage Management Appliance 2.1
- Microsoft JScript 5.1
- Microsoft JScript 5.6
- Microsoft VBScript 5.1
- Microsoft VBScript 5.6
- Nortel Networks CallPilot 1002rp
- Nortel Networks CallPilot 200i
- Nortel Networks CallPilot 201i
- Nortel Networks CallPilot 702t
- Nortel Networks CallPilot 703t
Run all software as a nonprivileged user with minimal access rights.
To limit the potential damage that successful exploits may achieve, run all nonadministrative software as an unprivileged user.
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 may indicate exploit attempts or activity that results from successful exploits.
Do not follow links provided by unknown or untrusted sources.
Attackers can exploit this vulnerability by enticing a user to visit a malicious website. Do not follow links provided by sources of questionable integrity. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.
Since exploiting this issue allows malicious script code to run in web clients, consider disabling support for script code and active content within the client browser. Note that this mitigation tactic might adversely affect websites that rely on the execution of browser-based script code.
Do not open email messages from unknown or untrusted individuals.
Attackers could exploit this vulnerability through HTML email messages. Do not accept any email from sources of questionable integrity.
The vendor has released a security advisory and fixes. Please see the references for more information.
Peter Ferrie of Symantec
© 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.