CVE-2007-2955
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple unspecified "input validation error" vulnerabilities in multiple ActiveX controls in NavComUI.dll, as used in multiple Norton AntiVirus, Internet Security, and System Works products for 2006, allows remote attackers to execute arbitrary code via (1) the AnomalyList property to AxSysListView32 and (2) Anomaly property to AxSysListView32OAA.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMultiple input validation vulnerabilities in NavComUI.dll ActiveX controls (AxSysListView32 and AxSysListView32OAA) in Norton 2006 products allow remote attackers to execute arbitrary code by passing specially crafted data through the AnomalyList and Anomaly properties.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2006= 2005= 2006= 2006CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Norton product versionOpen Control Panel > Programs and Features (or Add/Remove Programs), look for 'Symantec Norton' or 'Norton' products and check if version 2005 or 2006 is listedAffected if Any affected Norton product (Antivirus 2006, Internet Security 2005/2006, or System Works 2006) is installed
-
Locate NavComUI.dllSearch for NavComUI.dll in the Norton program directory (typically C:\Program Files\Norton...) or use command: dir /s C:\NavComUI.dllAffected if NavComUI.dll file exists on the system
-
Check for vulnerable ActiveX control registrationOpen Registry Editor and check HKEY_CLASSES_ROOT\CLSID for {4C43F7D2-0C5C-11D0-A3C9-00AA0061096D} (AxSysListView32) or {4C43F7D4-0C5C-11D0-A3C9-00AA0061096D} (AxSysListView32OAA)Affected if Either AxSysListView32 or AxSysListView32OAA CLSID is registered in the Windows registry
-
Verify ActiveX control is marked safe in Internet ExplorerCheck registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{CLSID} or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{CLSID} for the control's CLSID entriesAffected if The vulnerable ActiveX controls are registered as safe for scripting in Internet Explorer
A system is affected if any Norton 2005/2006 product is installed AND NavComUI.dll exists AND the AxSysListView32/AxSysListView32OAA ActiveX controls are registered on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince Norton 2006 products are end-of-life and likely unpatched, remove or replace the affected software. If continued use is required, disable ActiveX controls in Internet Explorer and implement network segmentation to limit exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-2955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data