# CVE-2009-0361: Privilege escalation in n/a

> Local attackers can overwrite arbitrary files and change ownership via KRB5CCNAME manipulation in setuid applications using pam-krb5.

- **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:** 13 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0361, DSA-1722-1, GHSA-rcf3-vv2f-fwg2

## What is CVE-2009-0361?

CVE-2009-0361 is a medium-severity vulnerability in n/a, published on 13 Feb 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Russ Allbery pam-krb5 before 3.13, as used by libpam-heimdal, su in Solaris 10, and other software, does not properly handle calls to pam_setcred when running setuid, which allows local users to overwrite and change the ownership of arbitrary files by setting the KRB5CCNAME environment variable, and then launching a setuid application that performs certain pam_setcred operations.

Weakness: CWE-264

## Which versions are affected by CVE-2009-0361?

It affects 1 product.


Products: Eyrie Pam-Krb5.

## How do I fix CVE-2009-0361?

Upgrade to a fixed version.

## Is CVE-2009-0361 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0360](https://insights.sbomify.com/CVE-2009-0360/): Privilege escalation in n/a (medium 6.2)
- [CVE-2009-1384](https://insights.sbomify.com/CVE-2009-1384/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0361 and fix it if it is affected.

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

## Sources

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

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