# CVE-2004-2073: Privilege escalation in n/a

> Local root users in Linux-VServer can escape the virtual server sandbox to access the host filesystem via a modified chroot exploit.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q2m5-737c-xfjv

## What is CVE-2004-2073?

CVE-2004-2073 is a high-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Linux-VServer 1.24 allows local users with root privileges on a virtual server to gain access to the filesystem outside the virtual server via a modified chroot-again exploit using the chmod command.

## Which versions are affected by CVE-2004-2073?


## How do I fix CVE-2004-2073?

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

## Is CVE-2004-2073 being exploited?

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

Public exploit code:

- Linux VServer Project 1.2x - Chroot Breakout (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2073 and fix it if it is affected.

What it is: CVE-2004-2073 is a high-severity vulnerability in n/a, published on 19 May 2005. 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-2004-2073 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-2004-2073/ (Markdown: https://insights.sbomify.com/CVE-2004-2073/index.md)
```

## Sources

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

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