# CVE-2001-0803: Memory corruption in n/a

> Remote attackers can execute arbitrary commands via a buffer overflow in the CDE Subprocess Control Service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p2mw-q26f-vf87

## What is CVE-2001-0803?

CVE-2001-0803 is a critical memory corruption vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the client connection routine of libDtSvc.so.1 in CDE Subprocess Control Service (dtspcd) allows remote attackers to execute arbitrary commands.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2001-0803?

It affects 1 product.


Products: Open Group Cde Common Desktop Environment.

## How do I fix CVE-2001-0803?

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

## Is CVE-2001-0803 being exploited?

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

Public exploit code:

- Solaris 8 dtspcd - Remote Heap Overflow (Metasploit) (exploitdb)
- Solaris dtspcd Heap Overflow (metasploit)
- Solaris dtspcd - Remote Heap Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0803 and fix it if it is affected.

What it is: CVE-2001-0803 is a critical memory corruption vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0803 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-2001-0803/ (Markdown: https://insights.sbomify.com/CVE-2001-0803/index.md)
```

## Sources

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

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