Linux Kernel up to 2.5 rose_route.c rose_rt_ioctl ndigis 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.
5.1$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 2.5. This issue affects the function rose_rt_ioctl of the file rose_route.c. Performing a manipulation of the argument ndigis results in access control. This vulnerability was named CVE-2005-3273. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 2.5 (Operating System). This affects the function rose_rt_ioctl of the file rose_route.c. The manipulation of the argument ndigis 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 integrity. The summary by CVE is:

The rose_rt_ioctl function in rose_route.c for Radionet Open Source Environment (ROSE) in Linux 2.6 kernels before 2.6.12, and 2.4 before 2.4.29, does not properly verify the ndigis argument for a new route, which allows attackers to trigger array out-of-bounds errors with a large number of digipeats.

The bug was discovered 03/18/2005. The weakness was presented 10/20/2005 by ryan with Coverity (Website). The advisory is shared at lkml.org. This vulnerability is uniquely identified as CVE-2005-3273 since 10/20/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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.

The vulnerability was handled as a non-public zero-day exploit for at least 194 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 21849 (CentOS 3 : kernel (CESA-2005:663)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117692 (CentOS Security Update for Kernel (CESA-2006:0579)).

Upgrading to version 2.6 eliminates this vulnerability. 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 (19738), Tenable (21849), SecurityFocus (BID 13886†), OSVDB (14864†) and Secunia (SA18056†). See VDB-1105, VDB-1106, VDB-1104 and VDB-1234 for similar entries. 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: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 21849
Nessus Name: CentOS 3 : kernel (CESA-2005:663)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 56014
OpenVAS Name: Debian Security Advisory DSA 922-1 (kernel-source-2.4.27)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 2.6

Timelineinfo

03/18/2005 🔍
06/07/2005 +81 days 🔍
06/07/2005 +0 days 🔍
09/28/2005 +113 days 🔍
10/20/2005 +22 days 🔍
10/20/2005 +0 days 🔍
10/20/2005 +0 days 🔍
10/20/2005 +0 days 🔍
12/15/2005 +56 days 🔍
07/03/2006 +200 days 🔍
07/25/2006 +22 days 🔍
03/11/2015 +3151 days 🔍
06/23/2019 +1565 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: lkml.org
Researcher: ryan
Organization: Coverity
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2005-3273 (🔍)
GCVE (CVE): GCVE-0-2005-3273
GCVE (VulDB): GCVE-100-26613

OVAL: 🔍

X-Force: 19738
SecurityFocus: 13886 - Linux Kernel Radionet Open Source Environment Unspecified Vulnerability
Secunia: 18056 - Debian update for kernel-source-2.6.8, Less Critical
OSVDB: 14864 - CVE-2005-3273 - Linux - Kernel - Unspecified Issue
SecurityTracker: 1014115
Vulnerability Center: 12343 - Linux Kernel Unspecified Vulnerability in ROSE, Medium

See also: 🔍

Entryinfo

Created: 03/11/2015 23:39
Updated: 06/23/2019 08:59
Changes: 03/11/2015 23:39 (83), 06/23/2019 08:59 (10)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!