# CVE-2000-0722: Race condition in n/a

> Local attackers can exploit a race condition in Helix GNOME Updater to install arbitrary RPM packages, leading to privilege escalation.

- **Severity:** Medium 6.2 (`AV:L/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gv87-4wrx-xhh7

## What is CVE-2000-0722?

CVE-2000-0722 is a medium-severity vulnerability in n/a, published on 21 Sep 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Helix GNOME Updater helix-update 0.5 and earlier allows local users to install arbitrary RPM packages by creating the /tmp/helix-install installation directory before root has begun installing packages.

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

It affects 1 product.


Products: Helix Code Gnome Updater.

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

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

## Is CVE-2000-0722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0722 is a medium-severity vulnerability in n/a, published on 21 Sep 2000. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2000-0722 in the wild and no public exploit code.

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-2000-0722/ (Markdown: https://insights.sbomify.com/CVE-2000-0722/index.md)
```

## Sources

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

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