# CVE-2011-1946: Privilege escalation in n/a

> Local attackers can gain elevated privileges by exploiting a logic error in gnomesu-pam-backend that ignores setuid/setgid failures.

- **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:** 7 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vqmh-h9f4-cvv4, openSUSE-SU-2024:10076-1

## What is CVE-2011-1946?

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

### Official description

gnomesu-pam-backend in libgnomesu 1.0.0 prints an error message but proceeds with the non-error code path upon failure of the setgid or setuid function, which allows local users to gain privileges by leveraging access to two unprivileged user accounts, and running many processes under one of these accounts.

Weakness: CWE-264

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgnomesu` | openSUSE:Tumbleweed | All versions | 2.0.0-2.3 |

Products: Hongli Lai Libgnomesu.

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

Apply the vendor's patch.

## Is CVE-2011-1946 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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