July 8, 2006
Microsoft Internet Explorer 6 is reportedly prone to a denial-of-service vulnerability because the application fails to perform boundary checks before copying user-supplied data into sensitive process buffers.
This issue is triggered when an attacker convinces a victim to activate a malicious ActiveX control object.
Remote attackers may exploit this issue to crash Internet Explorer 6, effectively denying service to legitimate users.
A stack-based heap overflow may be possible; as a result, remote code could run in the context of the user running the affected application. This has not been confirmed.
- Microsoft Internet Explorer 6.0
- Microsoft Internet Explorer 6.0 SP1
Do not follow links provided by unknown or untrusted sources.
Do not use production computers for visiting websites of unknown or questionable integrity.
Set web browser security to disable the execution of script code or active content.
To avoid exploits of this type, consider disabling active content and script controls that broswers use to render web pages.
Implement multiple redundant layers of security.
As an added precaution, deploy memory-protection schemes (such as nonexecutable stack/heap configuration and randomly mapped memory segments). This may complicate a successful exploit of memory-corruption vulnerabilities.
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: email@example.com.
hdm has been credited with the discovery of this vulnerability
Copyright © 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 firstname.lastname@example.org
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 email@example.com
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.