Linux Kernel 2.6.x dvb_ca_ioctl numeric error

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

Summaryinfo

A vulnerability was found in Linux Kernel 2.6.x. It has been classified as problematic. This issue affects the function dvb_ca_ioctl. This manipulation causes numeric error. This vulnerability is handled as CVE-2011-0521. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in Linux Kernel 2.6.x (Operating System) and classified as critical. Affected by this vulnerability is the function dvb_ca_ioctl. The manipulation with an unknown input leads to a numeric error vulnerability. The CWE definition for the vulnerability is CWE-189. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The dvb_ca_ioctl function in drivers/media/dvb/ttpci/av7110_ca.c in the Linux kernel before 2.6.38-rc2 does not check the sign of a certain integer field, which allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact via a negative value.

The weakness was released 01/25/2011 by Dan Carpenter with Kernel Team as confirmed git commit (GIT Repository). The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2011-0521 since 01/20/2011. An attack has to be approached locally. The requirement for exploitation is a single authentication. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 53399 (RHEL 5 : kernel (RHSA-2011:0429)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165558 (SUSE Enterprise Linux Security Update Linux Kernel (SUSE-SA:2011:019)).

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (64988), Tenable (53399), SecurityFocus (BID 45986†), OSVDB (70665†) and Secunia (SA43009†). Entries connected to this vulnerability are available at VDB-55715, VDB-57033, VDB-56997 and VDB-56640. 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: 8.8
VulDB Meta Temp Score: 7.7

VulDB Base Score: 8.8
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Numeric error
CWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 53399
Nessus Name: RHEL 5 : kernel (RHSA-2011:0429)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

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

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: git.kernel.org

Timelineinfo

01/19/2011 🔍
01/19/2011 +0 days 🔍
01/20/2011 +1 days 🔍
01/22/2011 +2 days 🔍
01/25/2011 +3 days 🔍
01/25/2011 +0 days 🔍
01/25/2011 +0 days 🔍
01/26/2011 +0 days 🔍
02/02/2011 +7 days 🔍
02/14/2011 +12 days 🔍
03/11/2011 +25 days 🔍
04/13/2011 +33 days 🔍
03/18/2021 +3627 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Researcher: Dan Carpenter
Organization: Kernel Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2011-0521 (🔍)
GCVE (CVE): GCVE-0-2011-0521
GCVE (VulDB): GCVE-100-4261

OVAL: 🔍
IAVM: 🔍

X-Force: 64988 - Linux Kernel av7110_ca.c privilege escalation, High Risk
SecurityFocus: 45986 - Linux Kernel 'drivers/media/dvb/ttpci/av7110_ca' IOCTL Local Privilege Escalation Vulnerability
Secunia: 43009 - Linux Kernel Multiple Vulnerabilities, Less Critical
OSVDB: 70665 - Linux Kernel drivers/media/dvb/ttpci/av7110_ca.c dvb_ca_ioctl() Function Crafted IOCTL Handling Memory Corruption
SecurityTracker: 1025195 - Linux Kernel AV7110 Driver dvb_ca_ioctl() Memory Corruption Error Lets Local Users Deny Service
Vulnerability Center: 29367 - Linux Kernel Prior to 2.6.38-rc2 Local Privilege Escalation Vulnerability, High

See also: 🔍

Entryinfo

Created: 02/14/2011 14:59
Updated: 03/18/2021 16:41
Changes: 02/14/2011 14:59 (90), 03/14/2017 11:47 (15), 03/18/2021 16:41 (3)
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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!