CVE-2010-4664 json
In ConsoleKit before 0.4.2, an intended security policy restriction bypass was found.
published 2019-11-13 6 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4629
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
In ConsoleKit before 0.4.2, an intended security policy restriction bypass was found. This flaw allows an authenticated system user to escalate their privileges by initiating a remote VNC session.
Patch / fix
- consolekit_project consolekit 0.4.2
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-2010-4664 updated cvss 6.5
ConsoleKit: Policy restrictions break-out via remote Virtual Network Computing (VNC) session
-
Red Hat Enterprise Linux 6 ConsoleKit, ConsoleKit-x11, ConsoleKit-libsaffected: no fix planned “Will not fix”
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.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- consolekit consolekit
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
security-tracker.debian.org
/tracker/CVE-2010-4664
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2010-4664
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2010-4664
third-party-advisory
Sources
- CVE List CVE-2010-4664
- NVD CVE-2010-4664
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.