Symantec SYMTDI.SYS Device Driver Local Denial of Service

2007-09-05T07:00:00
ID SMNTC-1134
Type symantec
Reporter Symantec Security Response
Modified 2020-03-06T14:03:30

Description

SUMMARY

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.

Risk Impact
Low

Remote Access

|

No

---|---

Local Access

|

Yes

Authentication Required

|

Yes, to the local system

Exploit available

|

No

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

ADDITIONAL PRODUCT INFORMATION

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

ISSUES

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.

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.

MITIGATION

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.

ACKNOWLEDGEMENTS

This issue was reported by Matousec-Transparent