# CVE-1999-0733: Buffer overflow in VMWare 1.0.1 for Linux via a long HOME environmental variable.


- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Mar 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-gw48-hr89-vwq9

## What is CVE-1999-0733?

CVE-1999-0733 is a high-severity vulnerability in Vmware Workstation, published on 22 Mar 2000. 

### Official description

Buffer overflow in VMWare 1.0.1 for Linux via a long HOME environmental variable.

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

It affects 1 product.


Products: Vmware Workstation.

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

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

## Is CVE-1999-0733 being exploited?

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

Public exploit code:

- VMware 1.0.1 - Local Buffer Overflow (exploitdb)

## Other vulnerabilities in Vmware Workstation

- [CVE-2019-5525](https://insights.sbomify.com/CVE-2019-5525/): Use after free in VMware Workstation (high 8.8)
- [CVE-2019-5511](https://insights.sbomify.com/CVE-2019-5511/): Path traversal in VMware Workstation (high 8.8)
- [CVE-2019-5512](https://insights.sbomify.com/CVE-2019-5512/): Privilege escalation in VMware Workstation (high 8.8)
- [CVE-2023-20854](https://insights.sbomify.com/CVE-2023-20854/): Path traversal in VMware Workstation (high 8.4)
- [CVE-2019-5526](https://insights.sbomify.com/CVE-2019-5526/): Privilege escalation in VMware Workstation (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0733 is a high-severity vulnerability in Vmware Workstation, published on 22 Mar 2000. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0733 exists.

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

## Sources

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

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