CVE-2006-4855: The \Device\SymEvent driver in Symantec Norton Personal Firewall 2006 9.1.0.33, and other versions of Norton Personal Firewall, Internet…
Noroxi assessment
Priority: Monitor (action score 19/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.3% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The \Device\SymEvent driver in Symantec Norton Personal Firewall 2006 9.1.0.33, and other versions of Norton Personal Firewall, Internet Security, AntiVirus, SystemWorks, Symantec Client Security SCS 1.x, 2.x, 3.0, and 3.1, Symantec AntiVirus Corporate Edition SAVCE 8.x, 9.x, 10.0, and 10.1, Symantec pcAnywhere 11.5 only, and Symantec Host, allows local users to cause a denial of service (system crash) via invalid data, as demonstrated by calling DeviceIoControl to send the data.
- Published
- Sep 19, 2006
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-399
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| symantec | client security | cpe:2.3:a:symantec:client_security |
| symantec | host ids | cpe:2.3:a:symantec:host_ids |
| symantec | norton antivirus | cpe:2.3:a:symantec:norton_antivirus |
| symantec | norton internet security | cpe:2.3:a:symantec:norton_internet_security |
| symantec | norton personal firewall | cpe:2.3:a:symantec:norton_personal_firewall |
| symantec | norton system works | cpe:2.3:a:symantec:norton_system_works |
| symantec | pcanywhere | cpe:2.3:a:symantec:pcanywhere |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- symantec client security1.0
- symantec client security1.0_build_8.01.9374
- symantec client security1.0.0_b8.01.9378
- symantec client security1.0.1
- symantec client security1.0.1_build_8.01.425a
- symantec client security1.0.1_build_8.01.429c
- symantec client security1.0.1_build_8.01.434
- symantec client security1.0.1_build_8.01.437
+12 more rows
- symantec client security1.0.1_build_8.01.446
- symantec client security1.0.1_build_8.01.457
- symantec client security1.0.1_build_8.01.460
- symantec client security1.0.1_build_8.01.464
- symantec client security1.0.1_build_8.01.471
- symantec client security1.0.1_build_8.01.501
- symantec client security1.1
- symantec client security1.1_stm_b8.1.0.825a
- symantec client security1.1.1
- symantec client security1.1.1_build_393
- symantec client security1.1.1_mr1_build_8.1.1.314a
- symantec client security1.1.1_mr2_build_8.1.1.319
Same product
symantec: all recordsOther highest-scoring records for the same primary product.
- CVE-2006-2630Stack-based buffer overflow in Symantec Antivirus 10.1 and Client Security 3.1 allows remote attackers to execute arbitrary code via…62This week
- CVE-2010-0107Buffer overflow in an ActiveX control (SYMLTCOM.dll) in Symantec N360 1.0 and 2.0; Norton Internet Security, AntiVirus, SystemWorks, and…39Monitor
- CVE-2007-3095Unspecified vulnerability in Symantec Reporting Server 1.0.197.0, and other versions before 1.0.224.0, as used in Symantec Client Security…37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2006-3454Sep 13, 2006 · Multiple format string vulnerabilities in Symantec AntiVirus Corporate Edition 8.1 up to 10.0, and Client Security 1.x up to 3.0, allow…28Monitor
- ← EarlierCVE-2006-4802Sep 14, 2006 · Format string vulnerability in the Real Time Virus Scan service in Symantec AntiVirus Corporate Edition 8.1 up to 10.0, and Client Security…18Monitor
- Later →CVE-2006-3455Oct 23, 2006 · The SAVRT.SYS device driver, as used in Symantec AntiVirus Corporate Edition 8.1 and 9.0.x up to 9.0.3, and Symantec Client Security 1.1…17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | dos | 2006-09-15 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-5 d
- Published
- TodayNov 16, 2026+7363 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- C
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:L/AC:L/Au:N/C:N/I:N/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (14 more)Show less
- securityreason.com/securityalert/1591
- securityresponse.symantec.com/avcenter/security/Content/2006.09.20a.html
- securitytracker.com/id?1016889
- securitytracker.com/id?1016892
- securitytracker.com/id?1016893
- securitytracker.com/id?1016894
- securitytracker.com/id?1016895
- securitytracker.com/id?1016896
- securitytracker.com/id?1016897
- securitytracker.com/id?1016898
- www.matousec.com/info/advisories/Norton-Insufficient-validation-of-SymEvent-driver-input-buffer.php
- www.securityfocus.com/archive/1/446111/100/0/threaded
- www.vupen.com/english/advisories/2006/3636
- exchange.xforce.ibmcloud.com/vulnerabilities/28960
Vendor advisories and official records. Exploit/PoC links are deliberately left out.