Revision History
| May 26, 2006 | - Updated Products Affected section and other details |
| May 27, 2006 | - Updated Products Affected section with update info |
| - Updated Unaffected Products section |
| May 30, 2006 | - Added CVE identifier |
| - Updated Products Affected section with update information |
| June 1, 2006 | - Updated Products Affected section |
| June 6, 2006 | - Updated Products Affected section |
| June 6, 2006 | - Updated information on localized product builds |
| November 29, 2006 | - Updated advisory to reflect the release of exploit code |
| January 17, 2007 | - Updated IPS signature update information |
| February 7, 2007 | - Updated NOTE section |
Impact
High
| Remote | Yes |
| Local | Yes |
| Authentication Required | No |
| Exploit publicly available | Yes |
Overview
A stack overflow in Symantec Client Security and Symantec AntiVirus Corporate Edition could potentially allow a remote or local attacker to execute code on the affected machine.
Products Affected
Note: All builds listed above are English versions only. Information on localized product builds can be found in the Upgrade Information section below. Please note that ALL builds of SAV 10.0 and 10.1 and SCS 3.0 and 3.1 prior to those listed in the Solutions column above are affected by this vulnerability
Unaffected Products
| Product | Version |
| Norton Product line | No products in the Norton product line are affected |
| Symantec AntiVirus Corporate Edition | 8.0, 8.1, 9.0 all builds |
| Symantec Client Security | 1.0, 1.1, 2.0, all builds |
Details
Symantec was notified that Symantec Client Security and Symantec AntiVirus Corporate Edition are susceptible to a potential stack overflow. Exploiting this overflow successfully could potentially cause a system crash, or allow a remote or local attacker to execute arbitrary code with System level rights on the affected system.
Symantec Response
Symantec engineers have verified that this vulnerability exists in the product versions listed above, and have provided updates for those products.
Upgrade Information
Available updates for English language versions are listed in the table above. Information on localized builds for other language versions, and information on upgrading, can be found in this KB Document:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006052609181248
Mitigation
Symantec Security Response has released virus definitions to detect several threats which attempt to exploit this vulnerability and vulnerabilities in several other products.
Symantec Security Response has also released IPS signatures to detect attempts to exploit this issue. The following updates are all available through LiveUpdate:
Symantec Network Security Appliance 7100:
SU 46 and later protect against attacks against port 2967. SU 46 was released in May, 2006.
SU 66 and later protect against attacks against port 2968. SU 66 was released on January 13, 2007.
Symantec Gateway Security 3.0:
SU 19 and later protect against attacks on port 2967. SU 19 was released in May 2006.
SU 34 and later protect against attacks on port 2968. SU 34 was released on January 12, 2007.
Symantec Client Security 2.0 and 3.0:
SU 22 and later protect against attacks on port 2967.
SU 44 and later protect against attacks on port 2968. SU 44 was released on January 12, 2007.
Symantec recommends customers immediately apply the latest Security Update to protect against potential related attacks.
To help reduce the risks associated with this vulnerability Symantec recommends the following best practices:
- Restrict access to administration or management systems to privileged users only, with additional restricted access to the physical host system(s) if possible.
- Keep all operating systems and applications updated with the latest vendor patches.
- Follow a multi-layered approach to security. Run both firewall and antivirus applications, at a minimum to provide multiple points of detection and protection to both inbound and outbound threats.
- Be cautious visiting unknown or untrusted websites or following unknown URL links.
- Do not open attachments or executables from unknown sources or that you didn't request or were unaware of. Always err on the side of caution. Even if the sender is known, the source address may be spoofed.
CVE
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. CVE has assigned the following identifier to this issue: CVE-2006-2630.
Credit
Symantec would like to thank eEye Digital Security (http://www.eeye.com) for reporting this issue, and working with us on the resolution.
Symantec takes the security and proper functionality of its products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec follows the principles of responsible disclosure. Symantec also subscribes to the vulnerability guidelines outlined by the National Infrastructure Advisory Council (NIAC). Please contact secure@symantec.com if you feel you have discovered a potential or actual security issue with a Symantec product. A Symantec Product Security team member will contact you regarding your submission.
Symantec has developed a Product Vulnerability Handling Process document outlining the process we follow in addressing suspected vulnerabilities in our products. We support responsible disclosure of all vulnerability information in a timely manner to protect Symantec customers and the security of the Internet as a result of vulnerability. This document is available from the location provided below.
Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be obtained from the location provided below.
Copyright (c) 2008 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: Thursday, 25-May-06 23:20:00
Last modified on: Wednesday, 07-Feb-07 23:19:43
Symantec Vulnerability Response Policy
Symantec Product Vulnerability Management PGP Key