# CVE-2004-2613: Missing authorization in n/a

> A vulnerability in Linux-VServer allows local users to modify specific proc entries, potentially leading to privilege escalation or data modification.

- **Severity:** Critical 10.0 (`AV:N/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:** 4 Dec 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f5h7-rm4x-whwq

## What is CVE-2004-2613?

CVE-2004-2613 is a critical missing authorization vulnerability in n/a, published on 4 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch for the 2.4 kernel before 1.3.5 has unspecified impact and attack vectors, related to "write access to specific proc entries from a vserver context", a different vulnerability than CVE-2004-2408.

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

It affects 1 product.


Products: Vserver Linux-Vserver.

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

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

## Is CVE-2004-2613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-1288](https://insights.sbomify.com/CVE-2003-1288/): Race condition in n/a (medium 5.0)
- [CVE-2004-2408](https://insights.sbomify.com/CVE-2004-2408/): Information disclosure in n/a (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2613 is a critical missing authorization vulnerability in n/a, published on 4 Dec 2005. 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-2004-2613 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-2004-2613/ (Markdown: https://insights.sbomify.com/CVE-2004-2613/index.md)
```

## Sources

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

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