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

> Attackers can read user clipboard data from QNX Neutrino RTOS by accessing a specific hex-encoded directory file.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cr68-36xq-733g

## What is CVE-2002-2409?

CVE-2002-2409 is a low-severity vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Photon microGUI in QNX Neutrino realtime operating system (RTOS) 6.1.0 and 6.2.0 allows attackers to read user clipboard information via a direct request to the 1.TEXT file in a directory whose name is a hex-encoded user ID.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Qnx Neutrino Rtos, Qnx Photon Microgui.

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

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

## Is CVE-2002-2409 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0618](https://insights.sbomify.com/CVE-2006-0618/): Code injection in n/a (medium 4.6)
- [CVE-2011-4060](https://insights.sbomify.com/CVE-2011-4060/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2409 is a low-severity vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2409 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-2409/ (Markdown: https://insights.sbomify.com/CVE-2002-2409/index.md)
```

## Sources

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

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