WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
September 13, 2006
Symantec AntiVirus Corporate Edition Elevation of Privilege

Revision History

Risk Impact

Remote AccessNo
Local AccessYes
Authentication RequiredYes
Exploit availableNo

An elevation of privilege vulnerability in Symantec Client Security and Symantec AntiVirus Corporate Edition could potentially allow a local attacker to execute code with elevated privileges on the target machine.

Affected Products
ProductVersionAffected BuildSolution
Symantec AntiVirus Corporate Edition10.0All builds prior to the solutionSAV 10 MR2 MP2 (SAV and later
Symantec AntiVirus Corporate Edition9.xAll builds prior to the solutionSAV 9 MR5 MP1 (SAV )and later
Symantec AntiVirus Corporate Edition8.1All builds prior to the solutionSAV 8.1.1 MR9 build 393 and later
Symantec Client Security 3.0All builds prior to the solutionSCS 3.0.2 MR2-MP2 - build 2020 and later
Symantec Client Security 2.xAll builds prior to the solutionSCS 2.0.5 MR5 MP 1 build 1100 and later
Symantec Client Security 1.xAll builds prior to the solutionSCS 1.1.1 MR9 build 393

SCS 1.1.1 MR9 will be available on fileconnect on the afternoon of September 13, 2006, US Pacific time. SCS 1.1.1 and SAV 8.1.1 MR9 are available in English and Japanese only. Symantec recommends that customers update to the international English version of SAV CE 8.1.1, or migrate to a non-vulnerable version of SAV Corporate Edition 9 or 10.

Symantec Platinum Support customers can also download product updates from the Platinum web site.

Unaffected Products
Symantec AntiVirus Corporate Edition10.1No build of SAV CE 10.1 is affected
Symantec Client Security3.1No build of SCS 3.1 is affected
Norton product lineallNone of the Norton products are affected

Layered Defense notified Symantec of a format string vulnerability within Symantec AntiVirus Corporate Edition. If successfully exploited, the vulnerability could allow a local attacker to execute code with elevated privileges on the local system.

Symantec AntiVirus Corporate Edition provides the ability to customize the alert notification message displayed when a virus is found or when the Tamper Protection function is triggered. The alert notification process does not properly validate the user-generated input. This could allow a local user to replace the Tamper Protection and Virus Alert Notification messages with a specially-crafted format string which could allow access to the process stack. If successfully exploited, this could allow the user to execute code of the attacker’s choice with elevated privileges, on the local system.

In addition, Symantec engineers found a second format string vulnerability in the alert notification process. This issue could allow a local user to replace the alert notification message with a format string which could cause potentially cause the Real Time Virus Scan service to crash when the notification message is displayed following the detection of a malicious file.

Symantec Response
Symantec engineers have verified that these vulnerabilities exist in the product versions listed in the table above, and have provided updates to address the issues.

Symantec is not aware of any customers impacted by either of these issues, or of any attempts to exploit them.

As a part of normal best practices, users should keep vendor-supplied patches for all application software and operating systems up-to-date. Symantec recommends any affected customers update their product to protect against these types of threats.

In a managed environment, administrators can lock the ability to change the notification messages. This option prevents users from easily changing the alert messages.

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

Symantec would like to thank Deral Heiland of Layered Defense (www.LayeredDefense.com) for reporting this issue, and working with us on the resolution.

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.

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

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

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, 13-Sep-06 11:00:00
Last modified on: Wednesday, 13-Sep-2006 11:16:22 PDT
[an error occurred while processing this directive]