# CVE-2006-2869: Other in n/a

> An unspecified vulnerability in the avast! CHM unpacker allows remote attackers to potentially compromise the system via malicious 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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gx46-m3qm-69wf

## What is CVE-2006-2869?

CVE-2006-2869 is a critical vulnerability in n/a, published on 6 Jun 2006. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in the CHM unpacker in avast! before 4.7.844 has unknown impact and remote attack vectors.

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

It affects 1 product.


Products: Alwil Avast Antivirus.

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

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

## Is CVE-2006-2869 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4626](https://insights.sbomify.com/CVE-2006-4626/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2385](https://insights.sbomify.com/CVE-2005-2385/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1719](https://insights.sbomify.com/CVE-2005-1719/): Unknown vulnerability in ALWIL avast! (high 7.5)
- [CVE-2006-1355](https://insights.sbomify.com/CVE-2006-1355/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-1770](https://insights.sbomify.com/CVE-2005-1770/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2869 is a critical vulnerability in n/a, published on 6 Jun 2006. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2869 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-2869/ (Markdown: https://insights.sbomify.com/CVE-2006-2869/index.md)
```

## Sources

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

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