# CVE-2002-1439: Memory corruption in n/a

> Stack corruption in HP-UX Virtualvault TGA daemon allows attackers to access system files and potentially escalate privileges.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wx48-6h8x-8mw4

## What is CVE-2002-1439?

CVE-2002-1439 is a medium-severity memory corruption vulnerability in n/a, published on 18 Mar 2003. It can be exploited over the network, with no action from the victim.

### Official description

Unknown vulnerability related to stack corruption in the TGA daemon for HP-UX 11.04 (VVOS) Virtualvault 4.0, 4.5, and 4.6 may allow attackers to obtain access to system files.

## Which versions are affected by CVE-2002-1439?

It affects 2 products.


Products: Hp Virtualvault, Hp Vvos.

## How do I fix CVE-2002-1439?

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

## Is CVE-2002-1439 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0763](https://insights.sbomify.com/CVE-2002-0763/): Auth bypass in n/a (high 7.5)
- [CVE-2002-1793](https://insights.sbomify.com/CVE-2002-1793/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0224](https://insights.sbomify.com/CVE-2005-0224/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0606](https://insights.sbomify.com/CVE-2001-0606/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1439 and fix it if it is affected.

What it is: CVE-2002-1439 is a medium-severity memory corruption vulnerability in n/a, published on 18 Mar 2003. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1439 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-2002-1439/ (Markdown: https://insights.sbomify.com/CVE-2002-1439/index.md)
```

## Sources

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

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