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

> Local attackers can exploit buffer overflows in HP Tru64 UNIX print utilities to gain elevated 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:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rr8v-qm4r-j8fq

## What is CVE-2002-1606?

CVE-2002-1606 is a medium-severity memory corruption vulnerability in Hp Hp-Ux, published on 25 Mar 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple buffer overflows in HP Tru64 UNIX 5.1a, 5.1, 5.0a, 4.0g, and 4.0f allow local users to gain privileges via (1) lpc, (2) lpd, (3) lpq, (4) lpr, or (5) lprm.

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

It affects 2 products.


Products: Hp Hp-Ux, Hp Tru64.

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

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

## Is CVE-2002-1606 being exploited?

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

## Other vulnerabilities in Hp Hp-Ux

- [CVE-2008-1668](https://insights.sbomify.com/CVE-2008-1668/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-1662](https://insights.sbomify.com/CVE-2008-1662/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-6425](https://insights.sbomify.com/CVE-2007-6425/): Denial of service in n/a (critical 10.0)
- [CVE-2007-6195](https://insights.sbomify.com/CVE-2007-6195/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4241](https://insights.sbomify.com/CVE-2007-4241/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1606 is a medium-severity memory corruption vulnerability in Hp Hp-Ux, published on 25 Mar 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1606 in the wild and no public exploit code.

Affected product: Hp Hp-Ux. 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-1606/ (Markdown: https://insights.sbomify.com/CVE-2002-1606/index.md)
```

## Sources

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

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