# CVE-2002-0793: Path traversal in n/a

> Local attackers can overwrite arbitrary files in QNX RTOS via hard link or symbolic link following vulnerabilities in specific utilities.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j97v-38wx-6pjj

## What is CVE-2002-0793?

CVE-2002-0793 is a medium-severity path traversal vulnerability in n/a, published on 26 Jul 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hard link and possibly symbolic link following vulnerabilities in QNX RTOS 4.25 (aka QNX4) allow local users to overwrite arbitrary files via (1) the -f argument to the monitor utility, (2) the -d argument to dumper, (3) the -c argument to crttrap, or (4) using the Watcom sample utility.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Blackberry Qnx Neutrino Real-Time Operating System.

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

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

## Is CVE-2002-0793 being exploited?

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

Public exploit code:

- QNX RTOS 4.25 - 'CRTTrap' File Disclosure (exploitdb)
- QNX RTOS 4.25 - monitor Arbitrary File Modification (exploitdb)
- QNX RTOS 4.25 - dumper Arbitrary File Modification (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0793 is a medium-severity path traversal vulnerability in n/a, published on 26 Jul 2002. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0793 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-2002-0793/ (Markdown: https://insights.sbomify.com/CVE-2002-0793/index.md)
```

## Sources

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

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