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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious LHA archive with a long filename in WinRAR.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 25 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3whr-c946-j943

## What is CVE-2006-3845?

CVE-2006-3845 is a critical memory corruption vulnerability in n/a, published on 25 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

Stack-based buffer overflow in lzh.fmt in WinRAR 3.00 through 3.60 beta 6 allows remote attackers to execute arbitrary code via a long filename in a LHA archive.

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

It affects 1 product.


Products: Rarlab Winrar.

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

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

## Is CVE-2006-3845 being exploited?

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

Public exploit code:

- RARLAB WinRAR 3.x - LHA Filename Handling Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2025-6218](https://insights.sbomify.com/CVE-2025-6218/): RARLAB WinRAR Path Traversal (high 7.8, exploited in the wild)
- [CVE-2023-38831](https://insights.sbomify.com/CVE-2023-38831/): RARLAB WinRAR Code Execution (high 7.8, exploited in the wild)
- [CVE-2018-20250](https://insights.sbomify.com/CVE-2018-20250/): WinRAR Absolute Path Traversal (high 7.8, exploited in the wild)
- [CVE-2008-7144](https://insights.sbomify.com/CVE-2008-7144/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1254](https://insights.sbomify.com/CVE-2004-1254/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3845 is a critical memory corruption vulnerability in n/a, published on 25 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3845 exists.

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-3845/ (Markdown: https://insights.sbomify.com/CVE-2006-3845/index.md)
```

## Sources

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

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