ConsoleKit up to 0.4.1 Security Policy privileges management

Summaryinfo

A vulnerability was found in ConsoleKit up to 0.4.1. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component Security Policy. This manipulation causes privileges management. This vulnerability appears as CVE-2010-4664. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in ConsoleKit up to 0.4.1 and classified as critical. Affected by this vulnerability is an unknown function of the component Security Policy. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 04/07/2011. The weakness was presented 11/13/2019. This vulnerability is known as CVE-2010-4664 since 01/03/2011. The attack can be launched remotely. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 50 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 55161 (SuSE 11.1 Security Update : ConsoleKit (SAT Patch Number 4613)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l.

Upgrading to version 0.4.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (55161) and OSVDB (74646†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• ConsoleKit

Version

• 0.4.0
• 0.4.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion