Revision History
None
Risk Impact
Low
| Remote Access | No |
| Local Access | Yes |
| Authentication Required | Yes, to the local system |
| Exploit available | No |
Overview
Some versions of Symantec’s device driver SYMTDI.SYS contain a vulnerability which, if successfully exploited, could allow a local attacker to cause the system to crash.
Affected Products
| Product | Version | Solution |
| Norton AntiSpam | 2005 | Run LiveUpdate in Interactive Mode |
| Norton AntiVirus | 2005,2006 | Run LiveUpdate in Interactive Mode |
| Norton Internet Security | 2005,2006 | Run LiveUpdate in Interactive Mode |
| Norton Personal Firewall | 2005,2006 | Run LiveUpdate in Interactive Mode |
| Norton System Works | 2005,2006 | Run LiveUpdate in Interactive Mode |
| Symantec AntiVirus Corporate Edition | 10.0.x | SAV 10.1 MR6 MP1 or later |
|   | 10.1.x |
| Symantec AntiVirus Corporate Edition | 9.x | SAV 9 MR6 MP1 |
| Symantec Client Security | 3.1.x | SCS 3.1 MR6 MP1 or later |
| 3.0.x |
| Symantec Client Security | 2.x | SCS 2.0 MR6 MP1 |
Note:
All builds prior to the listed solution are affected by this issue. For additional information on updating Symantec Client Security and Symantec AntiVirus Corporate Edition, please see this Knowledgebase article:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007090409431648
Unaffected Products
| Product | Version | Build |
| Norton 360 | all | all |
| Norton AntiBot | all | all |
| Norton Confidential | all | all |
| Norton AntiVirus | 2007and later | all |
| Norton Internet Security | 2007and later | all |
| Symantec AntiVirus Corporate Edition | 10.2.x | all |
| Symantec AntiVirus for Linux | 10.x | all |
Details
Symantec was notified of a potential denial of service vulnerability in the device driver SYMTDI.SYS. A specially crafted IRP sent to an IOCTL handler function could allow memory to be overwritten because the address space was not properly validated in some versions of the driver. A potential attacker must be logged into the 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 SYMTDI.SYS. However, to ensure all available updates have been applied, users can run a manual LiveUpdate as follows:
- Open any installed Norton product
- Click on LiveUpdate in the GUI
- Run LiveUpdate until all available product updates are downloaded and installed
- A system reboot is required for this update
Best Practices
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.
- Restrict access to computer systems to trusted users only.
- 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-1476 to this issue.
SecurityFocus has assigned BID 22977 to this vulnerability.
Symantec takes the security and proper functionality of its products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec follows the principles of responsible disclosure. Symantec also subscribes to the vulnerability guidelines outlined by the National Infrastructure Advisory Council (NIAC). Please contact secure@symantec.com if you feel you have discovered a potential or actual security issue with a Symantec product. A Symantec Product Security team member will contact you regarding your submission.
Symantec has developed a Product Vulnerability Handling Process document outlining the process we follow in addressing suspected vulnerabilities in our products. We support responsible disclosure of all vulnerability information in a timely manner to protect Symantec customers and the security of the Internet as a result of vulnerability. This document is available from the location provided below.
Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be obtained from the location provided below.
Copyright (c) 2008 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: Wednesday, 05-Sep-07 11:50:00
Last modified on: Thursday, 06-Sep-07 07:23:27