# CVE-2006-3654: Memory corruption in n/a

> Remote attackers can cause denial of service in Microsoft Works Spreadsheet via crafted Excel files, requiring user interaction to open the file.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fw4g-9jhm-9hgh

## What is CVE-2006-3654?

CVE-2006-3654 is a low-severity memory corruption vulnerability in Microsoft Works, published on 17 Jul 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in wksss.exe 8.4.702.0 in Microsoft Works Spreadsheet 8.0 allows remote attackers to cause a denial of service (CPU consumption or crash) via crafted Excel files.

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

It affects 1 product.


Products: Microsoft Works.

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

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

## Is CVE-2006-3654 being exploited?

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

## Other vulnerabilities in Microsoft Works

- [CVE-2012-2550](https://insights.sbomify.com/CVE-2012-2550/): Memory corruption in n/a (critical 9.3)
- [CVE-2006-3653](https://insights.sbomify.com/CVE-2006-3653/): Denial of service in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3654 is a low-severity memory corruption vulnerability in Microsoft Works, published on 17 Jul 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-3654 in the wild and no public exploit code.

Affected product: Microsoft Works. 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-3654/ (Markdown: https://insights.sbomify.com/CVE-2006-3654/index.md)
```

## Sources

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

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