Linux Kernel 2.6.16.9 find_keyring_by_name race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.7$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel 2.6.16.9. This issue affects the function find_keyring_by_name. This manipulation causes race condition. This vulnerability is handled as CVE-2010-1437. Additionally, an exploit exists.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel 2.6.16.9 (Operating System). Affected by this vulnerability is the function find_keyring_by_name. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect availability. The summary by CVE is:

Race condition in the find_keyring_by_name function in security/keys/keyring.c in the Linux kernel 2.6.34-rc5 and earlier allows local users to cause a denial of service (memory corruption and system crash) or possibly have unspecified other impact via keyctl session commands that trigger access to a dead keyring that is undergoing deletion by the key_cleanup function.

The issue has been introduced in 03/20/2006. The weakness was released 05/07/2010 (Website). The advisory is shared at patchwork.kernel.org. This vulnerability is known as CVE-2010-1437. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1509 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 47525 (Fedora 13 : kernel-2.6.33.5-112.fc13 (2010-9183)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 118295 (Fedora Update for Kernel (FEDORA-2010-9183)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (58254), Exploit-DB (33886), Tenable (47525), SecurityFocus (BID 39719†) and Vulnerability Center (SBV-26011†). Entries connected to this vulnerability are available at VDB-53670 and VDB-53477. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 3.8

VulDB Base Score: 4.0
VulDB Temp Score: 3.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 47525
Nessus Name: Fedora 13 : kernel-2.6.33.5-112.fc13 (2010-9183)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 67406
OpenVAS Name: Debian Security Advisory DSA 2053-1 (linux-2.6)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/20/2006 🔍
04/15/2010 +1486 days 🔍
04/27/2010 +12 days 🔍
04/27/2010 +0 days 🔍
05/07/2010 +10 days 🔍
05/07/2010 +0 days 🔍
06/10/2010 +34 days 🔍
07/01/2010 +21 days 🔍
03/19/2015 +1722 days 🔍
10/22/2024 +3505 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: dsa-2053
Status: Not defined
Confirmation: 🔍

CVE: CVE-2010-1437 (🔍)
GCVE (CVE): GCVE-0-2010-1437
GCVE (VulDB): GCVE-100-53101

OVAL: 🔍
IAVM: 🔍

X-Force: 58254
SecurityFocus: 39719 - Linux Kernel 'find_keyring_by_name()' Local Memory Corruption Vulnerability
Secunia: 39830
Vulnerability Center: 26011 - Linux kernel 2.6.34-rc5 and Prior Local DoS Vulnerability via Keyctl Session Commands, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/19/2015 12:22
Updated: 10/22/2024 22:02
Changes: 03/19/2015 12:22 (68), 02/27/2017 09:44 (8), 09/13/2021 07:45 (6), 09/13/2021 07:52 (1), 09/13/2021 07:58 (1), 10/22/2024 22:02 (23)
Complete: 🔍
Cache ID: 216:02C:103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!