# CVE-2006-4855: Denial of service in n/a

> Local attackers can crash the system by sending invalid data to the SymEvent driver in various Symantec security products.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-76wv-4mx9-c373

## What is CVE-2006-4855?

CVE-2006-4855 is a medium-severity denial of service vulnerability in Symantec Norton Antivirus, published on 19 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-399

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

It affects 7 products.


Products: Symantec Client Security, Symantec Host Ids, Symantec Norton Antivirus, Symantec Norton Internet Security, Symantec Norton Personal Firewall, Symantec Norton System Works, Symantec Pcanywhere.

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

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

## Is CVE-2006-4855 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4855 exists.

Public exploit code:

- Symantec (Multiple Products) - 'SymEvent' Driver Local Denial of Service (exploitdb)

## Other vulnerabilities in Symantec Norton Antivirus

- [CVE-2006-2630](https://insights.sbomify.com/CVE-2006-2630/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0107](https://insights.sbomify.com/CVE-2010-0107/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3095](https://insights.sbomify.com/CVE-2007-3095/): Auth bypass in n/a (critical 9.0)
- [CVE-2007-3021](https://insights.sbomify.com/CVE-2007-3021/): File upload in n/a (high 7.5)
- [CVE-2006-3454](https://insights.sbomify.com/CVE-2006-3454/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4855 is a medium-severity denial of service vulnerability in Symantec Norton Antivirus, published on 19 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4855 exists.

Affected product: Symantec Norton Antivirus. 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-4855/ (Markdown: https://insights.sbomify.com/CVE-2006-4855/index.md)
```

## Sources

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

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