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

> Local attackers with unmount permissions can gain privileges by using the umount -r option to clear security flags on file systems.

- **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:** Yes
- **Published:** 13 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2876, DSA-823-1, DSA-825-1, GHSA-96fj-vjjr-c856

## What is CVE-2005-2876?

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

### Official description

umount in util-linux 2.8 to 2.12q, 2.13-pre1, and 2.13-pre2, and other packages such as loop-aes-utils, allows local users with unmount permissions to gain privileges via the -r (remount) option, which causes the file system to be remounted with just the read-only flag, which effectively clears the nosuid, nodev, and other flags.

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

It affects 1 product.


Products: Andries Brouwer Util-Linux.

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

Apply the vendor's patch.

## Is CVE-2005-2876 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1147](https://insights.sbomify.com/CVE-2001-1147/): Information disclosure in n/a (high 7.2)
- [CVE-2001-1175](https://insights.sbomify.com/CVE-2001-1175/): Information disclosure in n/a (high 7.2)
- [CVE-2003-0094](https://insights.sbomify.com/CVE-2003-0094/): Weak cryptography in n/a (medium 5.0)
- [CVE-2004-0080](https://insights.sbomify.com/CVE-2004-0080/): Use after free in n/a (medium 5.0)
- [CVE-2006-7108](https://insights.sbomify.com/CVE-2006-7108/): Auth bypass in n/a (medium 4.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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