# CVE-2009-1756: Information disclosure in n/a

> Local attackers can read X session credentials from process arguments to hijack graphical sessions in SLiM.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1756, GHSA-9vgj-3874-c5g7

## What is CVE-2009-1756?

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

### Official description

SLiM Simple Login Manager 1.3.0 places the X authority magic cookie (mcookie) on the command line when invoking xauth from (1) app.cpp and (2) switchuser.cpp, which allows local users to access the X session by listing the process and its arguments.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Simone Rota Slim Simple Login Manager.

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

Apply the vendor's patch.

## Is CVE-2009-1756 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2945](https://insights.sbomify.com/CVE-2010-2945/): Path traversal in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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