# CVE-1999-0137: Memory corruption in n/a

> Local attackers can exploit a buffer overflow in the dip program to gain root access on Linux systems.

- **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:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6hwp-66fm-v8h9

## What is CVE-1999-0137?

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

### Official description

The dip program on many Linux systems allows local users to gain root access via a buffer overflow.

## Which versions are affected by CVE-1999-0137?

It affects 1 product.


Products: Fred N. Van Kempen Dip.

## How do I fix CVE-1999-0137?

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

## Is CVE-1999-0137 being exploited?

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

Public exploit code:

- Fred N. van Kempen dip 3.3.7 - Local Buffer Overflow (1) (exploitdb)
- Fred N. van Kempen dip 3.3.7 - Local Buffer Overflow (2) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0137 and fix it if it is affected.

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

## Sources

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

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