Linux Kernel 2.6.28.2 llc_ui_getname information disclosure

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.
5.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel 2.6.28.2 and classified as problematic. This affects the function llc_ui_getname. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2009-3001. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel 2.6.28.2 (Operating System). Affected by this vulnerability is the function llc_ui_getname. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

The llc_ui_getname function in net/llc/af_llc.c in the Linux kernel 2.6.31-rc7 and earlier does not initialize a certain data structure, which allows local users to read the contents of some kernel memory locations by calling getsockname on an AF_LLC socket.

The issue has been introduced in 12/25/2008. The weakness was disclosed 08/28/2009 by Jon Oberheide as Bug 519305 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2009-3001. The exploitation appears to be easy. 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. MITRE ATT&CK project uses the attack technique T1592 for this issue.

A public exploit has been developed in ANSI C. It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 246 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 44780 (Debian DSA-1915-1 : linux-2.6 - privilege escalation/denial of service/sensitive memory leak), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 195000 (Ubuntu Security Notification for Linux, Linux-source-2.6.15 Vulnerabilities (USN-852-1)).

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 (52732), Tenable (44780), SecurityFocus (BID 36126†) and Vulnerability Center (SBV-23872†). The entries VDB-50151, VDB-50149, VDB-49465 and VDB-49437 are pretty similar. 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: 6.2
VulDB Meta Temp Score: 5.6

VulDB Base Score: 6.2
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 44780
Nessus Name: Debian DSA-1915-1 : linux-2.6 - privilege escalation/denial of service/sensitive memory leak
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 66098
OpenVAS Name: Debian Security Advisory DSA 1915-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

12/25/2008 🔍
08/25/2009 +243 days 🔍
08/25/2009 +0 days 🔍
08/28/2009 +2 days 🔍
08/28/2009 +0 days 🔍
08/28/2009 +0 days 🔍
10/27/2009 +60 days 🔍
03/18/2015 +1968 days 🔍
12/09/2024 +3554 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: Bug 519305
Researcher: Jon Oberheide
Status: Not defined
Confirmation: 🔍

CVE: CVE-2009-3001 (🔍)
GCVE (CVE): GCVE-0-2009-3001
GCVE (VulDB): GCVE-100-49717

OVAL: 🔍

X-Force: 52732
SecurityFocus: 36126 - Linux Kernel 'net/llc/af_llc.c' Local Information Disclosure Vulnerability
Vulnerability Center: 23872 - Linux kernel <= 2.6.31-rc7 AF_LLC socket Local Memory Disclosure Vulnerability, Low

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

Entryinfo

Created: 03/18/2015 15:15
Updated: 12/09/2024 02:31
Changes: 03/18/2015 15:15 (63), 02/16/2017 10:03 (15), 08/20/2021 16:56 (5), 08/20/2021 17:04 (1), 12/09/2024 02:31 (19)
Complete: 🔍
Cache ID: 216::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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!