# CVE-2018-14345: Auth bypass in n/a

> Attackers with D-Bus access can unlock graphical sessions without passwords if ReuseSession is enabled, leading to unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-14345, GHSA-4wvx-qq9g-8hh9, UBUNTU-CVE-2018-14345

## What is CVE-2018-14345?

CVE-2018-14345 is a high-severity authentication bypass vulnerability in n/a, published on 17 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in SDDM through 0.17.0. If configured with ReuseSession=true, the password is not checked for users with an already existing session. Any user with access to the system D-Bus can therefore unlock any graphical session. This is related to daemon/Display.cpp and helper/backend/PamBackend.cpp.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-14345?

It affects 1 product.


Products: Sddm Project Sddm.

## How do I fix CVE-2018-14345?

Apply the vendor's patch.

## Is CVE-2018-14345 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14345 and fix it if it is affected.

What it is: CVE-2018-14345 is a high-severity authentication bypass vulnerability in n/a, published on 17 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-14345 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-2018-14345/ (Markdown: https://insights.sbomify.com/CVE-2018-14345/index.md)
```

## Sources

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

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