Linux Kernel 2.6.26.3 sbni_ioctl access control

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

Summaryinfo

A vulnerability was found in Linux Kernel 2.6.26.3. It has been rated as problematic. Affected by this issue is the function sbni_ioctl. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2008-3525. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel 2.6.26.3 (Operating System). This affects the function sbni_ioctl. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The sbni_ioctl function in drivers/net/wan/sbni.c in the wan subsystem in the Linux kernel 2.6.26.3 does not check for the CAP_NET_ADMIN capability before processing a (1) SIOCDEVRESINSTATS, (2) SIOCDEVSHWSTATE, (3) SIOCDEVENSLAVE, or (4) SIOCDEVEMANSIPATE ioctl request, which allows local users to bypass intended capability restrictions.

The bug was discovered 08/29/2008. The weakness was shared 09/03/2008 by Zachary Amsden (Website). The advisory is shared at redhat.com. This vulnerability is uniquely identified as CVE-2008-3525 since 08/07/2008. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 52 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 34480 (Fedora 9 : kernel-2.6.26.6-79.fc9 (2008-8929)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165703 (SUSE Enterprise Linux Security Update Linux Kernel (SUSE-SA:2008:051)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (44894), Tenable (34480), SecurityFocus (BID 31565†), OSVDB (48432†) and Secunia (SA32103†). The entries VDB-41704, VDB-44544, VDB-44542 and VDB-44325 are related to this item. 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.4
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.4
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 34480
Nessus Name: Fedora 9 : kernel-2.6.26.6-79.fc9 (2008-8929)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

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

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

07/13/2008 🔍
08/07/2008 +25 days 🔍
08/29/2008 +22 days 🔍
08/29/2008 +0 days 🔍
09/03/2008 +5 days 🔍
09/03/2008 +0 days 🔍
10/02/2008 +29 days 🔍
10/03/2008 +1 days 🔍
10/06/2008 +3 days 🔍
10/23/2008 +17 days 🔍
10/24/2008 +1 days 🔍
03/17/2015 +2335 days 🔍
08/17/2019 +1614 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: redhat.com
Researcher: Zachary Amsden
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2008-3525 (🔍)
GCVE (CVE): GCVE-0-2008-3525
GCVE (VulDB): GCVE-100-43869

OVAL: 🔍
IAVM: 🔍

X-Force: 44894
SecurityFocus: 31565 - Linux Kernel LDT Selector Local Privilege Escalation and Denial of Service Vulnerability
Secunia: 32103
OSVDB: 48432 - CVE-2008-3525 - Linux Kernel - Security Bypass Issue
SecurityTracker: 1020969
Vulnerability Center: 19649 - Linux Kernel 2.6.26.3 sbni_ioctl Function Vulnerability Allows Local Attacker to Bypass Restrictions, High
Vupen: ADV-2008-2511

See also: 🔍

Entryinfo

Created: 03/17/2015 16:11
Updated: 08/17/2019 21:17
Changes: 03/17/2015 16:11 (75), 08/17/2019 21:17 (19)
Complete: 🔍
Cache ID: 216:674: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 know what is going to be exploited?

We predict KEV entries!