cve.bz

CVE-2006-3455 symantec

no score yetEPSS 0.4%Fix available

symantec: no CVSS score yet. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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 and 2.0.x up to 2.0.3, allows local users to execute arbitrary code via a modified address for the output buffer argument to the DeviceIOControl function.
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2006-3455 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-3455?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-3455?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-3455 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
symantec:client_security1.1
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
symantec:client_security1.1.1_mr3_build_8.1.1.323
symantec:client_security1.1.1_mr4_build_8.1.1.329
symantec:client_security1.1.1_mr5_build_8.1.1.336
symantec:client_security1.1.1_mr6_b8.1.1.266
symantec:client_security1.1_stm_b8.1.0.825a
symantec:client_security2.0
symantec:client_security2.0.1
symantec:client_security2.0.1_build_9.0.1.1000:mr1
symantec:client_security2.0.2
symantec:client_security2.0.2_build_9.0.2.1000:mr2
symantec:client_security2.0.3
symantec:client_security2.0.3_build_9.0.3.1000:mr3
symantec:client_security2.0_scf_7.1
symantec:client_security2.0_stm_build_9.0.0.338
symantec:norton_antivirus8.1
symantec:norton_antivirus8.1.0.825a
symantec:norton_antivirus8.1.1
symantec:norton_antivirus8.1.1.319
symantec:norton_antivirus8.1.1.323
symantec:norton_antivirus8.1.1.329
symantec:norton_antivirus8.1.1.366
symantec:norton_antivirus8.1.1.377
symantec:norton_antivirus8.1.1_build8.1.1.314a
symantec:norton_antivirus8.1.1_build393
symantec:norton_antivirus8.01.434
symantec:norton_antivirus8.01.437
symantec:norton_antivirus8.01.446
symantec:norton_antivirus8.01.457
symantec:norton_antivirus8.01.460
symantec:norton_antivirus8.01.464
symantec:norton_antivirus8.01.471
symantec:norton_antivirus9.0.1
symantec:norton_antivirus9.0.1.1.1000
symantec:norton_antivirus9.0.1.1000
symantec:norton_antivirus9.0.2
symantec:norton_antivirus9.0.2.1000

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Symantec Remote Management RTVScan Exploit sid 2003250

References

Check your stackJSON