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

> Local attackers can execute arbitrary code via a buffer overflow in WinRAR triggered by long command-line arguments, requiring user interaction.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/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:** 6 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4cg6-r453-9frw

## What is CVE-2005-4620?

CVE-2005-4620 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jan 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

Buffer overflow in WinRAR 3.50 and earlier allows local users to execute arbitrary code via a long command-line argument.  NOTE: because this program executes with the privileges of the invoking user, and because remote programs do not normally have the ability to specify a command-line argument for this program, there may not be a typical attack vector for the issue that crosses privilege boundaries. Therefore this may not be a vulnerability.

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

It affects 1 product.


Products: Rarlab Winrar.

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

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

## Is CVE-2005-4620 being exploited?

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

Public exploit code:

- WinRAR 3.30 - 'Filename' Local Buffer Overflow (1) (exploitdb)
- WinRAR 3.30 - 'Filename' Local Buffer Overflow (2) (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-2005-4620 and fix it if it is affected.

What it is: CVE-2005-4620 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4620 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-2005-4620/ (Markdown: https://insights.sbomify.com/CVE-2005-4620/index.md)
```

## Sources

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

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