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

> Local attackers can gain privileges by exploiting improper handling of the LIBUIM_VANILLA environment variable in suid/sgid applications linked to libuim.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/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:** 5 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3149, DSA-895-1, DTSA-22-1, GHSA-jmr8-f36w-9vrj

## What is CVE-2005-3149?

CVE-2005-3149 is a medium-severity vulnerability in n/a, published on 5 Oct 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Uim 0.4.x before 0.4.9.1 and 0.5.0 and earlier does not properly handle the LIBUIM_VANILLA environment variable when a suid or sgid application is linked to libuim, such as immodule for Qt, which allows local users to gain privileges.

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

It affects 1 product.


Products: Uim Uim.

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

Upgrade to a fixed version.

## Is CVE-2005-3149 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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