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

> Improper handling of percent characters in Event Viewer logs can cause display issues and disrupt dependent processes, requiring local access to trigger.

- **Severity:** Medium 4.1 (`AV:A/AC:L/Au:S/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rvfm-gjh7-5x2v

## What is CVE-2006-6753?

CVE-2006-6753 is a medium-severity denial of service vulnerability in n/a, published on 27 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Event Viewer (eventvwr.exe) in Microsoft Windows does not properly display log data that contains '%' (percent) characters, which might make it impossible to use Event Viewer to determine the actual data that triggered an event, and might produce long strings that are not properly handled by certain processes that rely on Event Viewer.

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

It affects 1 product.


Products: Microsoft Windows Event Viewer.

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

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

## Is CVE-2006-6753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6753 is a medium-severity denial of service vulnerability in n/a, published on 27 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-6753 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-6753/ (Markdown: https://insights.sbomify.com/CVE-2006-6753/index.md)
```

## Sources

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

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