# CVE-2005-2659: Memory corruption in n/a

> Buffer overflow in CHM Lib allows attackers to execute arbitrary code or cause denial of service via malicious CHM files.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2659, GHSA-27vf-v322-7qf5

## What is CVE-2005-2659?

CVE-2005-2659 is a critical memory corruption vulnerability in n/a, published on 16 Nov 2005. 

### Official description

Buffer overflow in the LZX decompression in CHM Lib (chmlib) 0.35, as used in products such as KchmViewer, has unknown impact and attack vectors.

## Which versions are affected by CVE-2005-2659?

It affects 1 product.


Products: Jed Wing Chm Lib.

## How do I fix CVE-2005-2659?

Upgrade to a fixed version.

## Is CVE-2005-2659 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2930](https://insights.sbomify.com/CVE-2005-2930/): Memory corruption in n/a (medium 5.1)
- [CVE-2005-3318](https://insights.sbomify.com/CVE-2005-3318/): Memory corruption in n/a (medium 5.1)
- [CVE-2006-3178](https://insights.sbomify.com/CVE-2006-3178/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2659 and fix it if it is affected.

What it is: CVE-2005-2659 is a critical memory corruption vulnerability in n/a, published on 16 Nov 2005. 
Exploitation: There is no known exploitation of CVE-2005-2659 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-2005-2659/ (Markdown: https://insights.sbomify.com/CVE-2005-2659/index.md)
```

## Sources

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

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