CVE-2015-8316 json
Array index error in LightDM (aka Light Display Manager) 1.14.3, 1.16.x before 1.16.6 when the XDMCP server is enabled allows remote attack…
published 2017-09-06 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8200
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Array index error in LightDM (aka Light Display Manager) 1.14.3, 1.16.x before 1.16.6 when the XDMCP server is enabled allows remote attackers to cause a denial of service (process crash) via an XDMCP request packet with no address.
Patch / fix
- lightdm Debian 14, Debian 13, Debian 12 1.16.6-1
debian advisories DEBIAN-CVE-2015-8316
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2015-8316 updated cvss 4.3
lightdm: XDMCP request packet with no addresses crashes LightDM
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.75% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-129 Improper Validation of Array Index
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1284574
issue-tracking, third-party-advisory, vdb-entry
-
openwall.com
/lists/oss-security/2015/11/22/1
mailing-list, vdb-entry
-
bugs.launchpad.net
/lightdm/+bug/1516831
issue-tracking, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2015-8316
- NVD CVE-2015-8316
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.