CVE-2007-1476 json
The SymTDI device driver (SYMTDI.SYS) in Symantec Norton Personal Firewall 2006 9.1.1.7 and earlier, Internet Security 2005 and 2006, AntiV…
published 2007-03-16 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1470
- cvss
- 1.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 1
- Exploit-DB
Summary
The SymTDI device driver (SYMTDI.SYS) in Symantec Norton Personal Firewall 2006 9.1.1.7 and earlier, Internet Security 2005 and 2006, AntiVirus Corporate Edition 3.0.x through 10.1.x, and other Norton products, allows local users to cause a denial of service (system crash) by sending crafted data to the driver's \Device file, which triggers invalid memory access, a different vulnerability than CVE-2006-4855.
Timeline
- First public exploit (EDB-29743)
- Published
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-29743 Symantec 'SYMTDI.SYS' Device Driver - Local Denial of Service dos, 2007-03-15
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
matousec.com
/info/advisories/Norton-Insufficient-validation-of-SymTDI-driver-input-buffer.php
vendor-advisory
- symantec.com /avcenter/security/Content/2007.09.05.html
-
securityfocus.com
/archive/1/462926/100/0/threaded
mailing-list
-
marc.info
/?l=full-disclosure&m=117396596027148&w=2
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/33003
vdb-entry
-
securityfocus.com
/bid/22977
vdb-entry
-
osvdb.org
/35088
vdb-entry
-
securityreason.com
/securityalert/2438
third-party-advisory
-
securitytracker.com
/id?1018656
vdb-entry
Sources
- CVE List CVE-2007-1476
- NVD CVE-2007-1476
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.