CVE-2012-1111 json
lightdm before 1.0.9 does not properly close file descriptors before opening a child process, which allows local users to write to the ligh…
published 2014-10-27 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1145
- cvss
- 4.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
lightdm before 1.0.9 does not properly close file descriptors before opening a child process, which allows local users to write to the lightdm log or have other unspecified impact.
Patch / fix
- lightdm Debian 14, Debian 13, Debian 12 1.0.9-1
debian advisories DEBIAN-CVE-2012-1111
- lightdm openSUSE Tumbleweed 1.21.1-1.1
opensuse advisories openSUSE-SU-2024:10033-1
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.launchpad.net https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/927060 referenced PoC, tagged "exploit" by a source, unverified
- bugzilla.novell.com https://bugzilla.novell.com/show_bug.cgi?id=745339 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/oss-sec/2012/q1/566 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/oss-sec/2012/q1/557 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
bugs.launchpad.net
/ubuntu/+source/lightdm/+bug/927060
exploit
-
bugzilla.novell.com
/show_bug.cgi?id=745339
exploit
-
seclists.org
/oss-sec/2012/q1/566
mailing-list, exploit
-
seclists.org
/oss-sec/2012/q1/557
mailing-list, exploit
-
lists.opensuse.org
/opensuse-updates/2012-03/msg00019.html
vendor-advisory
Sources
- CVE List CVE-2012-1111
- NVD CVE-2012-1111
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.