# CVE-2002-2039: Information disclosure in n/a

> Local users can access sensitive information from core dumps in QNX RTOS by triggering a segmentation fault in the su binary.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 14 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-27g9-qccj-r7jh

## What is CVE-2002-2039?

CVE-2002-2039 is a low-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

/bin/su in QNX realtime operating system (RTOS) 4.25 and 6.1.0 allows local users to obtain sensitive information from core dump files by sending the SIGSERV (invalid memory reference) signal.

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

It affects 1 product.


Products: Qnx Rtos.

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

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

## Is CVE-2002-2039 being exploited?

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

Public exploit code:

- QNX RTOS 4.25/6.1 - su Password Hash Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1390](https://insights.sbomify.com/CVE-2004-1390/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-1528](https://insights.sbomify.com/CVE-2005-1528/): Path traversal in n/a (high 7.2)
- [CVE-2006-0621](https://insights.sbomify.com/CVE-2006-0621/): Memory corruption in n/a (high 7.2)
- [CVE-2006-0623](https://insights.sbomify.com/CVE-2006-0623/): Privilege escalation in n/a (high 7.2)
- [CVE-2002-2040](https://insights.sbomify.com/CVE-2002-2040/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2039 is a low-severity vulnerability in n/a, published on 14 Jul 2005. 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-2039 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-2039/ (Markdown: https://insights.sbomify.com/CVE-2002-2039/index.md)
```

## Sources

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

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