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

> Local attackers can exploit a buffer overflow in ClearCase db_loader via the TERM variable to gain root privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 22 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wq48-hj2m-499j

## What is CVE-2001-0855?

CVE-2001-0855 is a high-severity memory corruption vulnerability in n/a, published on 22 Nov 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in db_loader in ClearCase 4.2 and earlier allows local users to gain root privileges via a long TERM environment variable.

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

It affects 1 product.


Products: Rational Software Clearcase.

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

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

## Is CVE-2001-0855 being exploited?

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

Public exploit code:

- Rational ClearCase 3.2/4.x - DB Loader TERM Environment Variable Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-0350](https://insights.sbomify.com/CVE-1999-0350/): Race condition in n/a (medium 6.2)
- [CVE-2002-1322](https://insights.sbomify.com/CVE-2002-1322/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0855 is a high-severity memory corruption vulnerability in n/a, published on 22 Nov 2001. 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-2001-0855 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-0855/ (Markdown: https://insights.sbomify.com/CVE-2001-0855/index.md)
```

## Sources

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

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