# CVE-2002-0498: Privilege escalation in n/a

> Local users with specific UID/GID can modify TotalView files to gain privileges as other users.

- **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:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hrx7-hjrh-ww2p

## What is CVE-2002-0498?

CVE-2002-0498 is a medium-severity vulnerability in n/a, published on 11 Jun 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Etnus TotalView 5.0.0-4 installs certain files with UID 5039 and GID 59, which could allow local users with that UID or GID to modify the files and gain privileges as other TotalView users.

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

It affects 1 product.


Products: Etnus Totalview.

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

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

## Is CVE-2002-0498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0498 is a medium-severity vulnerability in n/a, published on 11 Jun 2002. 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-0498 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-0498/ (Markdown: https://insights.sbomify.com/CVE-2002-0498/index.md)
```

## Sources

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

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