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

> A buffer overflow in email clients allows remote attackers to execute arbitrary code by sending a specially crafted MIME message.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fwjc-rphw-659w

## What is CVE-1999-0004?

CVE-1999-0004 is a medium-severity memory corruption vulnerability in Sco Unixware, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MIME buffer overflow in email clients, e.g. Solaris mailtool and Outlook.

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

It affects 3 products.


Products: Hp Dtmail, Sco Unixware, University of Washington Pine.

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

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

## Is CVE-1999-0004 being exploited?

There is no known exploitation of CVE-1999-0004 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0004 is a medium-severity memory corruption vulnerability in Sco Unixware, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-1999-0004 in the wild and no public exploit code.

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

## Sources

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

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