CVE-2013-2190
Summary
| CVE | CVE-2013-2190 |
|---|---|
| State | PUBLISHED |
| Assigner | redhat |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2013-10-17 23:55:04 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | The translate_hierarchy_event function in x11/clutter-device-manager-xi2.c in Clutter, when resuming the system, does not properly handle XIQueryDevice errors when a device has "disappeared," which causes the gnome-shell to crash and allows physically proximate attackers to access the previous gnome-shell session via unspecified vectors. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
LocalAccess Complexity
LowAuthentication
NoneConfidentiality
PartialIntegrity
NoneAvailability
NoneAV:L/AC:L/Au:N/C:P/I:N/A:N
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| x11: trap errors when calling XIQueryDevice (d343cc62) · Commits · GNOME / clutter · GitLab | af854a3a-2127-422b-91ae-364da2661108 | git.gnome.org | |
| Bug 701974 – x11: trap errors when calling XIQueryDevice | af854a3a-2127-422b-91ae-364da2661108 | bugzilla.gnome.org | |
| 980111 – (CVE-2013-2190) CVE-2013-2190 clutter: Improper translation of hierarchy events (gnome-shell crash after system resume) | af854a3a-2127-422b-91ae-364da2661108 | bugzilla.redhat.com | |
| x11: trap errors when calling XIQueryDevice (e310c68d) · Commits · GNOME / clutter · GitLab | af854a3a-2127-422b-91ae-364da2661108 | git.gnome.org | Exploit, Patch |
| openSUSE-SU-2013:1540-1: moderate: clutter: fixed a crash after system r | af854a3a-2127-422b-91ae-364da2661108 | lists.opensuse.org | Vendor Advisory |
| oss-security - Re: CVE request: gnome-shell crash, screen unlock on resume | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.