Microsoft Outlook Express And Windows Mail Common Library Integer Overflow Vulnerability



Date Discovered

May 11, 2010


Microsoft Outlook Express and Windows Mail are prone to a remote integer-overflow vulnerability because the applications fail to perform boundary checks on integer values. Successfully exploiting this issue will allow an attacker to execute arbitrary code with the privileges of the currently logged-in user. Failed exploit attempts will result in a denial-of-service condition.

Technologies Affected

  • Avaya Meeting Exchange - Client Registration Server
  • Avaya Meeting Exchange - Recording Server
  • Avaya Meeting Exchange - Streaming Server
  • Avaya Meeting Exchange - Web Conferencing Server
  • Avaya Meeting Exchange - Webportal
  • Avaya Messaging Application Server 4
  • Avaya Messaging Application Server 5
  • Avaya Messaging Application Server
  • Avaya Messaging Application Server MM 1.1
  • Avaya Messaging Application Server MM 2.0
  • Avaya Messaging Application Server MM 3.0
  • Avaya Messaging Application Server MM 3.1
  • 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
  • Microsoft Windows Live Mail
  • Microsoft Windows Mail


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 successful exploits.

Do not use client software to access unknown or untrusted hosts from critical systems.
Do not connect to unsuspecting mail servers.

Implement multiple redundant layers of security.
Memory-protection schemes such as nonexecutable stack and heap configurations and randomly mapped memory segments will complicate exploit of memory-corruption vulnerabilities.

When possible, limit the privileges granted to users to the least amount required.
To reduce the impact of latent vulnerabilities, limit user privileges to the least amount possible. This can help prevent privileged functions from running.

The vendor released patches and an advisory. Please see the references for more information.




© 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


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 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.