A notification window displayed by Symantecís Real-Time protection service could be exploited by a local user to gain elevated privileges on the local system.
|Symantec AntiVirus Corporate Edition||9.0||SAV 9.0.6 MR6 MP1- build 1100 or later http://www.symantec.com/enterprise/support/all_products.jsp |
|10.0||10.1.4 MR4 MP1- build 4010 or later http://www.symantec.com/enterprise/support/all_products.jsp |
|Symantec Client Security||2.0 ||SCS 2.0.6 MR6 MP1 - build 1100 or later http://www.symantec.com/enterprise/support/all_products.jsp|
|3.0||SCS 3.1.4 MR4 MP1 - build 4010 or later http://www.symantec.com/enterprise/support/all_products.jsp|
*All versions and builds prior to the version listed under Solution are affected.
Symantec AntiVirus Corporate Edition 10.0 (SAV CE) users can obtain this update by migrating to SAV CE 10.1MR4 MP1 or later. Symantec Client Security (SCS) 3.0 users can obtain the update by migrating to SCS 3.1 MR4 MP1 or later. Symantec Platinum Support customers can also download updates from the Platinum Web site.
|Norton Product line||All|
|Symantec AntiVirus Corporate Edition||10.2, all builds|
|Symantec AntiVirus for Linux||All|
The Real-Time scanner (RTVScan) component of Symantec Antivirus Corporate Edition provides notification and logging services for the product. One function of RTVScan is to display a notification window with information about a threat found on the system, if the program is configured to use that option. Ali Rahbar notified Symantec that an unprivileged user could potentially attack this window with specially crafted code, and gain SYSTEM level privileges on their local system. The user could then run code of their choice on their local system.
Symantec engineers have verified that the issue exists in the versions of Symantec AntiVirus Corporate Edition listed in the table above. Our investigation showed that the potential attack is limited to the local user, and that the elevation of privilege is limited to the userís own system.
Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.
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 immediately to protect against potential attempts to exploit this issue.
In a managed environment, administrators can disable Notification Message (alert) window, and lock the notification option to prevent users from re-enabling the Notification Message window.
Symantec recommends any affected customers update their product to protect against potential attempts to exploit this issue. 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.
Symantec would like to thank Ali Rahbar of Sysdream (http://www.sysdream.com) for reporting this issue.
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. A CVE identifier has been requested for this vulnerability.
SecurityFocus (http://www.securityfocus.com) has assigned Bugtraq ID (BID) 24810 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 firstname.lastname@example.org 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 email@example.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.
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 firstname.lastname@example.org.
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 email@example.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: Tuesday, 26-Jun-07 12:00:00
Last modified on: Friday, 13-Jul-07 16:16:02