# CVE-2011-4105: Path traversal in n/a

> Local attackers can exploit a symlink vulnerability in LightDM to change ownership of arbitrary files, potentially leading to privilege escalation.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:P/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:** 17 Feb 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4105, GHSA-vwp3-7r9h-7h5c

## What is CVE-2011-4105?

CVE-2011-4105 is a low-severity path traversal vulnerability in n/a, published on 17 Feb 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

LightDM before 1.0.6 allows local users to change ownership of arbitrary files via a symlink attack on ~/.Xauthority.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Robert Ancell Lightdm.

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

Upgrade to a fixed version.

## Is CVE-2011-4105 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1111](https://insights.sbomify.com/CVE-2012-1111/): Information disclosure in n/a (medium 4.6)
- [CVE-2013-4331](https://insights.sbomify.com/CVE-2013-4331/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4105 is a low-severity path traversal vulnerability in n/a, published on 17 Feb 2012. 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-4105 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-4105/ (Markdown: https://insights.sbomify.com/CVE-2011-4105/index.md)
```

## Sources

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

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