# CVE-2000-0438: Memory corruption in n/a

> Local users in the floppy group can execute arbitrary commands via a buffer overflow in fdmount, leading to privilege escalation.

- **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:** 12 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fg2g-48g8-4xwm

## What is CVE-2000-0438?

CVE-2000-0438 is a high-severity memory corruption vulnerability in Slackware Slackware Linux, published on 12 Jul 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in fdmount on Linux systems allows local users in the "floppy" group to execute arbitrary commands via a long mountpoint parameter.

## Which versions are affected by CVE-2000-0438?

It affects 4 products.


Products: Caldera Openlinux, Slackware Slackware Linux, Suse Suse Linux, Turbolinux Turbolinux.

## How do I fix CVE-2000-0438?

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

## Is CVE-2000-0438 being exploited?

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

Public exploit code:

- S.u.S.E Linux 4.x/5.x/6.x/7.0 / Slackware 3.x/4.0 / Turbolinux 6 / OpenLinux 7.0 - 'fdmount' Local Buffer Overflow (1) (exploitdb)
- S.u.S.E Linux 4.x/5.x/6.x/7.0 / Slackware 3.x/4.0 / Turbolinux 6 / OpenLinux 7.0 - 'fdmount' Local Buffer Overflow (2) (exploitdb)
- S.u.S.E Linux 4.x/5.x/6.x/7.0 / Slackware 3.x/4.0 / Turbolinux 6 / OpenLinux 7.0 - 'fdmount' Local Buffer Overflow (3) (exploitdb)

## Other vulnerabilities in Slackware Slackware Linux

- [CVE-2001-0850](https://insights.sbomify.com/CVE-2001-0850/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-0844](https://insights.sbomify.com/CVE-2000-0844/): Code injection in n/a (critical 10.0)
- [CVE-2000-0917](https://insights.sbomify.com/CVE-2000-0917/): Code injection in n/a (critical 10.0)
- [CVE-2000-0374](https://insights.sbomify.com/CVE-2000-0374/): Misconfiguration in n/a (critical 10.0)
- [CVE-2000-0370](https://insights.sbomify.com/CVE-2000-0370/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0438 and fix it if it is affected.

What it is: CVE-2000-0438 is a high-severity memory corruption vulnerability in Slackware Slackware Linux, published on 12 Jul 2000. 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-2000-0438 exists.

Affected product: Slackware Slackware Linux. 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-2000-0438/ (Markdown: https://insights.sbomify.com/CVE-2000-0438/index.md)
```

## Sources

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

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