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

> Local attackers can execute arbitrary code via a buffer overflow in bctool during unmount operations using long pathnames.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g9ch-8fx3-4rwr

## What is CVE-2001-0759?

CVE-2001-0759 is a high-severity memory corruption vulnerability in n/a, published on 12 Oct 2001. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in bctool in Jetico BestCrypt 0.8.1 and earlier allows local users to execute arbitrary code via a file or directory with a long pathname, which is processed during an unmount.

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

It affects 1 product.


Products: Jetico Bestcrypt.

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

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

## Is CVE-2001-0759 being exploited?

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

Public exploit code:

- BestCrypt 0.6/0.7/0.8 - BCTool UMount Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1345](https://insights.sbomify.com/CVE-2001-1345/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0759 is a high-severity memory corruption vulnerability in n/a, published on 12 Oct 2001. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0759 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-0759/ (Markdown: https://insights.sbomify.com/CVE-2001-0759/index.md)
```

## Sources

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

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