# CVE-2005-2807: Privilege escalation in n/a

> Local attackers can read arbitrary files and potentially escalate privileges by exploiting improper privilege dropping in frox when running setuid root.

- **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:** 7 Sep 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-395p-wxvj-rq46

## What is CVE-2005-2807?

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

### Official description

frox 0.7.18, when running setuid root, does not properly drop privileges when reading a configuration file, which allows local users to read portions of arbitrary files via the -f command line option.

## Which versions are affected by CVE-2005-2807?

It affects 1 product.


Products: Frox Frox.

## How do I fix CVE-2005-2807?

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

## Is CVE-2005-2807 being exploited?

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

Public exploit code:

- Frox 0.7.18 - Arbitrary Configuration File Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2808](https://insights.sbomify.com/CVE-2005-2808/): Auth bypass in n/a (high 7.5)
- [CVE-2001-0936](https://insights.sbomify.com/CVE-2001-0936/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2807 and fix it if it is affected.

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

## Sources

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

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