May 9, 2006
Microsoft Exchange Server is prone to a vulnerability that may let attackers execute code remotely. This issue is exposed when the server handles emails that contain malicious calendar data that is included in meeting requests. If the issue is successfully exploited, this could completely compromise the computer hosting the mail server.
- Microsoft Exchange Server 2000
- Microsoft Exchange Server 2000 SP1
- Microsoft Exchange Server 2000 SP2
- Microsoft Exchange Server 2003 SP1
- Microsoft Exchange Server 2003
- Microsoft Exchange Server 2003 SP2
Disallow anonymous access to services. Permit access for trusted individuals only.
If appropriate for the organization, require authentication for email clients. While this will eliminate the risk of anonymous attacks, the server will still be vulnerable to attacks by authenticated users.
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 exploitation attempts or activity that results from successful exploitation.
Implement multiple redundant layers of security.
Memory-protection schemes such as non-executable stack/heap configurations and randomly mapped memory segments may complicate exploitation of various code-execution vulnerabilities.
Microsoft has released a security bulletin to address supported versions of Microsoft Exchange Server.
The discoverer of this issue is not known.
© 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.