# CVE-2006-4266: Security feature bypass in n/a

> Local attackers with administrative privileges can bypass Norton Personal Firewall protections by modifying registry keys to load malicious libraries.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wvr4-w8j2-frwr

## What is CVE-2006-4266?

CVE-2006-4266 is a low-severity vulnerability in n/a, published on 21 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Symantec Norton Personal Firewall 2006 9.1.0.33, and possibly earlier, does not properly protect Norton registry keys, which allows local users to provide Trojan horse libraries to Norton by using RegSaveKey and RegRestoreKey to modify HKLM\SOFTWARE\Symantec\CCPD\SuiteOwners, as demonstrated using NISProd.dll.  NOTE: in most cases, this attack would not cross privilege boundaries, because modifying the SuiteOwners key requires administrative privileges.  However, this issue is a vulnerability because the product's functionality is intended to protect against privileged actions such as this.

## Which versions are affected by CVE-2006-4266?

It affects 1 product.


Products: Symantec Norton Personal Firewall.

## How do I fix CVE-2006-4266?

No fix has been published for CVE-2006-4266 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-4266 being exploited?

There is no known exploitation of CVE-2006-4266 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2002-1778](https://insights.sbomify.com/CVE-2002-1778/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-1779](https://insights.sbomify.com/CVE-2002-1779/): Security feature bypass in n/a (high 7.5)
- [CVE-2007-1495](https://insights.sbomify.com/CVE-2007-1495/): Denial of service in n/a (medium 4.9)
- [CVE-2002-2336](https://insights.sbomify.com/CVE-2002-2336/): Denial of service in n/a (medium 4.3)
- [CVE-2006-3725](https://insights.sbomify.com/CVE-2006-3725/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4266 and fix it if it is affected.

What it is: CVE-2006-4266 is a low-severity vulnerability in n/a, published on 21 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4266 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-4266/ (Markdown: https://insights.sbomify.com/CVE-2006-4266/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4266
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4266
- OSV: https://osv.dev/vulnerability/CVE-2006-4266

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-4266/
Summaries are generated and may contain mistakes; the official description above is the record.