# CVE-2011-3145: mount.ecrpytfs_private sets group owner of /etc/mtab to user's primary group

> Local attackers can escalate privileges because mount.ecryptfs_private fails to set the effective group ID, allowing unauthorized modification of mtab.

- **Severity:** Low 3.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L`)
- **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:** 22 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-3145, GHSA-r6pf-mxwq-6rrh

## What is CVE-2011-3145?

CVE-2011-3145 is a low-severity vulnerability in n/a, published on 22 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When mount.ecrpytfs_private before version 87-0ubuntu1.2 calls setreuid() it doesn't also set the effective group id. So when it creates the new version, mtab.tmp, it's created with the group id of the user running mount.ecryptfs_private.

Weakness: CWE-254

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

It affects 1 product.


Products: Mount.ecrpytfs Private Project Mount.ecrpytfs Private.

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

Apply the vendor's patch.

## Is CVE-2011-3145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3145 is a low-severity vulnerability in n/a, published on 22 Apr 2019. 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-3145 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-3145/ (Markdown: https://insights.sbomify.com/CVE-2011-3145/index.md)
```

## Sources

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

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