# CVE-2004-0771: Memory corruption in n/a

> Buffer overflow in LHA allows arbitrary code execution via a long command line option, requiring user interaction to process the malicious input.

- **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 needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vpgp-fv4q-4fgr

## What is CVE-2004-0771?

CVE-2004-0771 is a critical memory corruption vulnerability in n/a, published on 5 Aug 2004. 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 the extract_one function from lhext.c in LHA may allow attackers to execute arbitrary code via a long w (working directory) command line option, a different issue than CVE-2004-0769. NOTE: this issue may be REJECTED if there are not any cases in which LHA is setuid or is otherwise used across security boundaries.

## Which versions are affected by CVE-2004-0771?

It affects 1 product.


Products: Tsugio Okamoto Lha.

## How do I fix CVE-2004-0771?

Apply the vendor's patch.

## Is CVE-2004-0771 being exploited?

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

Public exploit code:

- LHA 1.x - 'extract_one' Multiple Buffer Overflow Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0745](https://insights.sbomify.com/CVE-2004-0745/): Command injection in n/a (critical 10.0)
- [CVE-2004-0694](https://insights.sbomify.com/CVE-2004-0694/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0771 and fix it if it is affected.

What it is: CVE-2004-0771 is a critical memory corruption vulnerability in n/a, published on 5 Aug 2004. 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-2004-0771 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-2004-0771/ (Markdown: https://insights.sbomify.com/CVE-2004-0771/index.md)
```

## Sources

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

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