Security readout for executives and security teams
Plain-English summary
SDDM through 0.17.0 could let a local user unlock another user's graphical session without that user's password when ReuseSession=true is configured. This is most urgent for shared Linux desktops, kiosks, lab machines, and jump boxes using SDDM.
Executive priority
Treat as high priority where SDDM is used on shared graphical systems. The risk is local but can expose an already logged-in user's desktop without their password.
Technical view
The issue is an authentication bypass in SDDM session reuse handling. With ReuseSession=true, SDDM did not check the password for users with an existing session, allowing any user with system D-Bus access to unlock any graphical session. The cited fix touches daemon/Display.cpp and helper/backend/PamBackend.cpp.
Likely exposure
Exposure appears limited to systems running SDDM through 0.17.0 with ReuseSession=true and local access to system D-Bus. Single-user workstations are lower risk than shared graphical systems.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack requires local system access, not remote network-only access.
Researcher notes
Evidence is concise but specific: the CVE names ReuseSession=true, system D-Bus access, and affected SDDM code paths. No CVSS, CWE, CPE, or exploitation telemetry is provided in the bundle.
Mitigation direction
- Review vendor guidance for patched SDDM packages.
- Upgrade SDDM beyond affected 0.17.0 versions where available.
- Disable ReuseSession unless operationally required.
- Prioritize shared desktops, kiosks, lab systems, and jump hosts.
- Restrict local account access on affected systems.
Validation and detection
- Inventory Linux systems using SDDM as display manager.
- Check installed SDDM version against affected through 0.17.0.
- Review SDDM configuration for ReuseSession=true.
- Confirm vendor package changelog includes the cited fix.
- Test session-lock behavior only in an authorized lab.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-14345 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.suse.com/show_bug.cgi?id=1101450CVE reference · x_refsource_CONFIRM
- https://github.com/sddm/sddm/commit/147cec383892d143b5e02daa70f1e7def50f5d98CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.