June 14, 2005
Microsoft Outlook Express is prone to a buffer overflow when parsing NNTP responses. Successful exploits could allow arbitrary code to run in the context of the user running the application.
- Microsoft Outlook Express 5.0
- Microsoft Outlook Express 5.5
- Microsoft Outlook Express 5.5 SP1
- Microsoft Outlook Express 5.5 SP2
- Microsoft Outlook Express 6.0
- Microsoft Outlook Express 6.0 SP1
Block external access at the network boundary, unless external parties require service.
Block outgoing connections to NNTP services on TCP/UDP port 119 if such access is not explicitly required. If appropriate, allow outgoing connections to trusted servers only.
Do not use client software to access unknown or untrusted hosts from critical systems.
This vulnerability could be exploited only by connecting to a malicious NNTP server. Connect to only known or trusted NNTP servers from critical systems.
Implement multiple redundant layers of security.
Memory-protection schemes such as nonexecutable stack/heap configurations and randomly mapped memory segments may complicate exploitation of memory-corruption vulnerabilities.
Run all software as a nonprivileged user with minimal access rights.
Attackers could exploit this vulnerability to execute arbitrary code in the security context of the current user. Running applications as an unprivileged user with minimal access rights will limit the consequences of successful exploitation of this and other latent vulnerabilities.
Microsoft has released fixes for supported versions of the software.
Reported by an anonymous source.
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 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.