# CVE-2011-1832: Missing authorization in n/a

> Local attackers can remove directories via umount due to improper mountpoint permission checks in ecryptfs-utils.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** 15 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1832, GHSA-fjxf-xqv9-mrff

## What is CVE-2011-1832?

CVE-2011-1832 is a low-severity missing authorization vulnerability in n/a, published on 15 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

utils/mount.ecryptfs_private.c in ecryptfs-utils before 90 does not properly check mountpoint permissions, which allows local users to remove directories via a umount system call.

Weakness: CWE-264

## Which versions are affected by CVE-2011-1832?

It affects 2 products.


Products: Ecryptfs Ecryptfs-Utils, Ecryptfs Ecryptfs Utils.

## How do I fix CVE-2011-1832?

Upgrade to a fixed version.

## Is CVE-2011-1832 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9687](https://insights.sbomify.com/CVE-2014-9687/): Weak cryptography in n/a (medium 5.0)
- [CVE-2011-1831](https://insights.sbomify.com/CVE-2011-1831/): Privilege escalation in n/a (medium 4.6)
- [CVE-2011-1836](https://insights.sbomify.com/CVE-2011-1836/): Missing authorization in n/a (medium 4.6)
- [CVE-2011-1835](https://insights.sbomify.com/CVE-2011-1835/): Race condition in n/a (medium 4.4)
- [CVE-2011-1837](https://insights.sbomify.com/CVE-2011-1837/): Privilege escalation in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1832 and fix it if it is affected.

What it is: CVE-2011-1832 is a low-severity missing authorization vulnerability in n/a, published on 15 Feb 2014. 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-2011-1832 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-2011-1832/ (Markdown: https://insights.sbomify.com/CVE-2011-1832/index.md)
```

## Sources

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

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