WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
SYM07-016
July 11, 2007
Symantec Client Security Internet E-mail Auto-Protect Stack Overflow

Revision History
7/16/2007 - Corrected the CVE candidate number

Severity
Low

Remote AccessNo
Local AccessYes
Authentication RequiredYes
Exploit publicly availableNo

Overview
A stack overflow in Symantec Anti-Virus Corporate Editionís Internet Email Auto-Protect feature could potentially crash the Internet Email scanning feature.

Affected Products
ProductVersionSolution
Symantec AntiVirus Corporate Edition 9.x, all builds prior to the solution SAV 9 MR6 (SAV 9.0.6.1000) or later https://fileconnect.symantec.com/
10.0 , all builds Upgrade to version 10.1 or later https://fileconnect.symantec.com/
Symantec Client Security 2.0.x, all builds prior to the solution Symantec Client Security 2.0.6 MR6 (build 1000-31) or later https://fileconnect.symantec.com/
3.0.x, all builds Upgrade to SCS 3.1 or later https://fileconnect.symantec.com/

NOTE: Platinum Support and Premium Support customers can also download the updates from the Platinum Support Web site.

Unaffected Products
ProductVersionBuild
Symantec AntiVirus Corporate Edition 10.1 all
10.2 all
Symantec Client Security 3.1 all
Symantec Antivirus for Linux all all
Norton AntiVirus all all
Norton Internet Security all all

Details
Symantec AntiVirus Corporate Editionís Internet E-mail Auto-Protect feature protects incoming and outgoing email messages that use the POP3 or SMTP communications protocol. When Internet E-mail Auto-Protect is enabled, an outgoing email with more than 951 characters in the To:, From: or Subject: fields could cause a stack overflow. The stack overflow could crash the Internet E-mail real-time protection service, resulting in a local denial of service. Subsequent outgoing SMTP email messages will not be scanned if the service has crashed.

File system Auto-Protect (real-time scanning), scheduled scanning, and on-demand scanning are not affected if the Internet E-mail scanning services has stopped, and these features will continue to function.

This issue was reported to Symantec by Jordi Corrales.

Symantec response
Symantec engineers have confirmed that this vulnerability exists in the products listed above, and have provided updates to resolve the issue.

This vulnerability exists only in the Internet E-mail Auto-Protect feature, and it can be exploited only if the feature is enabled on the userís system. The Lotus Notes and Microsoft Exchange Auto-Protect plug-ins are not impacted by this vulnerability.

Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.

Mitigation
Disable Internet E-Mail Auto-Protect, if the feature is not needed. Administrators can lock this option to ensure that users cannot accidentally re-enable it.

Best Practices
Symantec recommends any affected customers update their product immediately to protect against potential attempts to exploit this vulnerability. As part of normal best practices, Symantec recommends the following:

  • Run under the principle of least privilege to limit the impact of exploits.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Follow a multi-layered approach to security. Run both firewall and antivirus software to provide multiple points of detection and protection from inbound and outbound threats.
  • Use network intrusion detection systems to monitor network traffic for signs of anomalous activity. This may aid in detection of attacks related to exploitation of vulnerabilities.

Credit
Symantec would like to thank Jordi Corrales for reporting this issue.

References
This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2007-3771 to this issue

SecurityFocus (http://www.securityfocus.com) has assigned Bugtraq ID (BID) 24802 to this issue.


Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).

Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the end of this message.

Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Symantec-Product-Vulnerability-Response Symantec Vulnerability Response Policy Symantec Product Vulnerability Management PGP Key Symantec Product Vulnerability Management PGP Key


Copyright (c) 2009 by Symantec Corp.
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 secure@symantec.com.

Disclaimer
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 secure@symantec.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.


Initial Post on: Wednesday, 11-Jul-07 8:00:00
Last modified on: Tuesday, 17-Jul-07 13:25:37