1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec SPBBCDRV.SYS Device Driver Local Denial of Service


December 12, 2008

Revision History


Risk Impact


Remote Access (adjacent network)No
Local AccessYes
Authentication RequiredYes
Exploit availableYes*

*Proof of concept only


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

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


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

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


This issue was reported by Matousec-Transparent.


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.


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 has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
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 secure@symantec.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 secure@symantec.com.
The Symantec Software Security PGP key can be found at the following location:
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 secure@symantec.com.
Last modified on: December 12, 2008
Security Response Blog
The State of Spam