# CVE-2015-8308: Auth bypass in n/a

> Local users can bypass X server authentication due to missing -auth flag in LXDM, allowing unauthorized access to graphical sessions.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8308, GHSA-fchm-m3gc-4jjg

## What is CVE-2015-8308?

CVE-2015-8308 is a high-severity authentication bypass vulnerability in n/a, published on 24 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

LXDM before 0.5.2 did not start X server with -auth, which allows local users to bypass authentication with X connections.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2015-8308?

It affects 1 product.


Products: Lxdm Project Lxdm.

## How do I fix CVE-2015-8308?

Upgrade to a fixed version.

## Is CVE-2015-8308 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8308 and fix it if it is affected.

What it is: CVE-2015-8308 is a high-severity authentication bypass vulnerability in n/a, published on 24 Aug 2017. 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-2015-8308 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-2015-8308/ (Markdown: https://insights.sbomify.com/CVE-2015-8308/index.md)
```

## Sources

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

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