November 9, 2006: Minor update to clarify the affected versions of SAV 8.1
|Exploit publicly available||No|
Symantec was notified of a vulnerability in a device driver which, if successfully exploited, could allow a local attacker to execute arbitrary code with elevated privileges or to crash the system.
|Symantec AntiVirus Corporate Edition||8.1 all versions earlier than the solution||8.1.1 MR9|
|Symantec AntiVirus Corporate Edition||9.0.3 and earlier||9.0.4 MR4 build 1000 or later|
|Symantec Client Security||1.1||1.1.1 MR9 Build 393|
|Symantec Client Security||2.0.3 and earlier||2.0.4 MR4 build 1000|
|Symantec AntiVirus Corporate Edition||10.x||all|
|Symantec AntiVirus Corporate Edition||9.0.4 and later||all|
|Symantec Client Security||3.x||all|
|Norton AntiVirus||2005 and later||all|
|Norton Internet Security||2005 and later||all|
|Norton System Works||2005 and later||all|
Boon Seng Lim notified Symantec of a vulnerability in SAVRT.SYS which could allow a malicious user to use the output buffer of DeviceIOControl() to overwrite kernel addresses because the address space of the output buffer was not properly validated. A successful exploit could potentially allow a local attacker to execute code of their choice with elevated privileges, or to crash the system.
Symantec engineers verified that this issue exists in the products listed in the table above, and have released updates to address currently supported affected products.
Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.
As a part of normal best practices, Symantec recommends that users keep all application software and operating systems up-to-date with the latest vendor supplied patches.
Symantec would like to thank Boon Seng Lim for reporting this issue, and working with us on the resolution.
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-2006-3455 to this issue