WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
SYM08-022
12 December, 2008
Symantec SPBBCDRV.SYS Device Driver Local Denial of Service

Revision History
None

Risk Impact
Medium

Remote AccessNo
Local AccessYes
Authentication RequiredYes
Exploit publicly availableYes*


*Proof of concept only

Overview
Some versions of Symantecís device driver SPBBCDRV.SYS contain a vulnerability which, if successfully exploited, could allow a local attacker to cause the system to crash.

Affected Products
ProductVersionSolution(s)
Norton 3601.xRun LiveUpdate in Interactive Mode
Norton AntiSpam2004, 2005Run LiveUpdate in Interactive Mode
Norton AntiVirus2004 through 2008Run LiveUpdate in Interactive Mode
Norton Internet Security2004 through 2008Run LiveUpdate in Interactive Mode
Norton Personal Firewall2004, 2005, 2006Run LiveUpdate in Interactive Mode
Norton System Works2004, 2005, 2006Run LiveUpdate in Interactive Mode
Symantec AntiVirus Corporate Edition10.0.x, allSAV 10.1 MR7 and later
10.1.x, all versions prior to the fix
Symantec Client Security 3.0.xSCS 3.1 MR7 and later
3.1.x ,all versions prior to the fix

Unaffected Products
ProductVersionBuild
Norton 3602.xall
Norton Confidentialallall
Norton AntiVirus2009 and laterall
Norton AntiVirus Gaming Editionallall
Norton Internet Security2009 and laterall
Norton Personal Firewall2009 and laterall
Symantec AntiVirus Corporate Edition9.xall
Symantec AntiVirus Corporate Edition10.2all
Symantec AntiVirus for Linux1.xall
Symantec Client Security 2.xall
Symantec Endpoint Protection 11.xall


Details
Symantec was notified of a potential Denial of Service (DoS) vulnerability in the Symantec device driver SPBBCDRV.SYS. The vulnerability is caused by a failure to validate arguments sent to NtCreateMutant and NtOpenEvent.

A potential attacker must be logged into the target computer to attempt an exploit. A successful exploit of this vulnerability could potentially allow that user to crash their computer.

Symantec response
Symantec engineers have verified that the vulnerability exists in the products listed in the Affected Products table above, and have provided updates to correct the problem.

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

Updating Consumer (Norton) products
Symantec Norton product users who regularly launch and run LiveUpdate should already have received an updated (non-vulnerable) version of SPBBCDRV.SYS. However, to ensure all available updates have been applied, users can run a manual LiveUpdate as follows:

  • Open any installed Norton product
  • Click LiveUpdate
  • Run LiveUpdate until all available product updates are downloaded and installed
  • A system reboot is required for this update

Best Practice
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 attempted exploits.
  • Limit access to trusted users.
  • 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.

Credit
This issue was reported by Matousec-Transparent.

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-1793 to this issue.

SecurityFocus has assigned BugTraq ID (BID) 23241 to this vulnerability.


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: Tuesday, 26-Jun-07 12:00:00
Last modified on: Thursday, 11-Dec-08 18:43:49