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

> Local attackers can exploit RSBAC jail restrictions to gain elevated privileges via specific system calls.

- **Severity:** High 7.2 (`AV:L/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:** 13 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cmcm-62j3-r8fh

## What is CVE-2004-0667?

CVE-2004-0667 is a high-severity vulnerability in Gentoo Linux, published on 13 Jul 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Rule Set Based Access Control (RSBAC) 1.2.2 through 1.2.3 allows access to sys_creat, sys_open, and sys_mknod inside jails, which could allow local users to gain elevated privileges.

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

It affects 2 products.


Products: Gentoo Linux, Rsbac Rule Set Based Access Control.

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

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

## Is CVE-2004-0667 being exploited?

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

## Other vulnerabilities in Gentoo Linux

- [CVE-2004-0914](https://insights.sbomify.com/CVE-2004-0914/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1037](https://insights.sbomify.com/CVE-2004-1037/): Command injection in n/a (critical 10.0)
- [CVE-2004-1034](https://insights.sbomify.com/CVE-2004-1034/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0891](https://insights.sbomify.com/CVE-2004-0891/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1337](https://insights.sbomify.com/CVE-2002-1337/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0667 is a high-severity vulnerability in Gentoo Linux, published on 13 Jul 2004. 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-0667 in the wild and no public exploit code.

Affected product: Gentoo Linux. 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-0667/ (Markdown: https://insights.sbomify.com/CVE-2004-0667/index.md)
```

## Sources

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

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