Revision History 2.19.2010 Updated to note that this issue requires “Local Access” and cannot be done remotely.
3.1.2010 Removed and explicitly declared SEP 11.x not vulnerable. Added Dr. Brooke Stevens as one of the finders.
3.2.2010 Removed references to SEP 11.x, clarified questions on tamper protection.
|Exploit publicly available
Overview On-demand scanning with Symantec AntiVirus can be bypassed by denying read access to user files.
||Upgrade to MR9**
|Symantec Client Security
||Upgrade to MR9**
*SEP 11.x is not vulnerable to this issue.
** Along with the Best Practices described below, Symantec recommends running Symantec AntiVirus with Tamper Protection enabled and set to “block” mode to further mitigate malicious attacks against the product
Details Symantec was notified of a means to potentially bypass an on-demand scan in Symantec AntiVirus.
If Symantec Tamper protection is disabled, it is possible to potentially bypass scanning by having another entity deny read access to Symantec AntiVirus Protection.
Should an attacker succeed in passing sufficient specific events to the application, on-demand scans could potentially cease to run. The application will no longer accept the user’s current token degrading the on-demand scan capability while the user remains logged on.
Symantec Response Symantec product engineers have released MR9 for the Symantec Products listed above that fix the issue. Symantec recommends that all customers apply the latest available updates to protect against threats of this nature.
Symantec also recommends that the Symantec Tamper Protection be enabled and set to “block” for all customers who use Symantec AntiVirus.
Symantec is not aware of any exploitation of or adverse customer impact from these issues.
Mitigation If Customers of Symantec AntiVirus 10.1.x are unable to upgrade to the latest available updates, Symantec recommends that Symantec Tamper Protection be enabled and set to “block” to aid in mitigation of possible threat.
As part of normal best practices, Symantec strongly recommends:
- Restrict access to administration or management systems to privileged users.
- Restrict remote access, if required, to trusted/authorized systems only.
- Run under the principle of least privilege where possible to limit the impact of exploit by threats.
- Keep all operating systems and applications updated with the latest vendor patches.
- Follow a multi-layered approach to security.
- Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
- Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities
Credit Symantec would like to thank Jeffrey Walton and Dr. Brooke Stephens for reporting this issue and coordinating with Symantec for resolution.
Security Focus, http://www.securityfocus.com
, has assigned a Bugtraq ID (BID)38219 to these issues for inclusion in the Security Focus vulnerability database.
These issues are candidates for inclusion in the CVE list (http://cve.mitre.org
), which standardizes names for security problems. The CVE initiative has assigned
CVE-2010-0106 to this issue
REPORTING VULNERABILITIES TO SYMANTEC
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 responsible disclosure guidelines
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC)
practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact email@example.com
if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to firstname.lastname@example.org
The Symantec Software Security PGP key can be found at the following location:
COPYRIGHT (C) 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 Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com