Linux Kernel 2.6.33/2.6.34 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.
4.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel 2.6.33/2.6.34. It has been classified as problematic. This issue affects some unknown processing. This manipulation causes information disclosure. This vulnerability is registered as CVE-2010-4525. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel 2.6.33/2.6.34 (Operating System). It has been declared as problematic. Affected by this vulnerability is an unknown code block. 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:

Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.

The issue has been introduced in 02/24/2010. The weakness was published 01/10/2011 by Stephan Mueller as Bug CVE-201 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2010-4525. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 95 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 63968 (RHEL 5 : kvm (RHSA-2011:0028)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165182 (SUSE Security Update for Kernel (SUSE-SA:2011:020)).

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 X-Force (64519), Tenable (63968), SecurityFocus (BID 45676†), OSVDB (70377†) and Vulnerability Center (SBV-29331†). Similar entries are available at VDB-13218, VDB-67522, VDB-56096 and VDB-56006. 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: 4.0

VulDB Base Score: 4.0
VulDB Temp Score: 4.0
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: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 63968
Nessus Name: RHEL 5 : kvm (RHSA-2011:0028)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 870652
OpenVAS Name: RedHat Update for kernel RHSA-2011:0007-01
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/24/2010 🔍
05/30/2010 +95 days 🔍
12/09/2010 +192 days 🔍
01/05/2011 +27 days 🔍
01/10/2011 +5 days 🔍
01/10/2011 +0 days 🔍
01/10/2011 +0 days 🔍
01/12/2011 +2 days 🔍
01/23/2011 +10 days 🔍
01/24/2013 +732 days 🔍
03/19/2015 +784 days 🔍
01/20/2025 +3595 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: Bug CVE-201
Researcher: Stephan Mueller
Status: Not defined

CVE: CVE-2010-4525 (🔍)
GCVE (CVE): GCVE-0-2010-4525
GCVE (VulDB): GCVE-100-56005

OVAL: 🔍

X-Force: 64519
SecurityFocus: 45676 - Linux Kernel 'kvm_vcpu_events.interrupt.pad' Field Local Information Disclosure Vulnerability
Secunia: 42890
OSVDB: 70377 - Linux Kernel kvm_vcpu_events.interrupt.pad Structure Member Stack Memory Local Disclosure
Vulnerability Center: 29331 - Linux Kernel 2.6.33 through 2.6.34-rc6 Local information Disclosure Vulnerability, Low

See also: 🔍

Entryinfo

Created: 03/19/2015 23:27
Updated: 01/20/2025 19:32
Changes: 03/19/2015 23:27 (65), 03/14/2017 11:42 (12), 10/11/2021 12:26 (4), 10/11/2021 12:32 (1), 01/20/2025 19:32 (16)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!