# CVE-2002-2038: Denial of service in n/a

> Local users can cause denial of service or spoof files in threaded processes using NGPT's filesystem-based shared memory.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/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:** 14 Jul 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v2rg-8fwx-qrf3

## What is CVE-2002-2038?

CVE-2002-2038 is a low-severity denial of service 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

Next Generation POSIX Threading (NGPT) 1.9.0 uses a filesystem-based shared memory entry, which allows local users to cause a denial of service or in threaded processes or spoof files via unknown methods.

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

It affects 1 product.


Products: Bill Abt Next Generation Posix Threading.

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

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

## Is CVE-2002-2038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2038 is a low-severity denial of service 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: There is no known exploitation of CVE-2002-2038 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-2038/ (Markdown: https://insights.sbomify.com/CVE-2002-2038/index.md)
```

## Sources

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

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