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

> Local attackers can exploit a buffer overflow in GNOME libraries to gain root privileges via crafted arguments in applications like nethack.

- **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 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6fm6-5ph4-2rpq

## What is CVE-1999-1477?

CVE-1999-1477 is a high-severity memory corruption vulnerability in Mandrakesoft Mandrake Linux, published on 12 Sep 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in GNOME libraries 1.0.8 allows local user to gain root access via a long --espeaker argument in programs such as nethack.

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

It affects 2 products.


Products: Gnome Gnome Libs, Mandrakesoft Mandrake Linux.

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

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

## Is CVE-1999-1477 being exploited?

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

Public exploit code:

- Mandriva Linux Mandrake 6.0 / Gnome Libs 1.0.8 - 'espeaker' Local Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-1477 is a high-severity memory corruption vulnerability in Mandrakesoft Mandrake Linux, published on 12 Sep 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-1999-1477 exists.

Affected product: Mandrakesoft Mandrake 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-1999-1477/ (Markdown: https://insights.sbomify.com/CVE-1999-1477/index.md)
```

## Sources

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

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