Linux Kernel 2.6.28.2 parse_tag_3_packet memory corruption

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.
8.8$5k-$25k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Linux Kernel 2.6.28.2. The impacted element is the function parse_tag_3_packet. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2009-2407. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel 2.6.28.2 (Operating System). This affects the function parse_tag_3_packet. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Heap-based buffer overflow in the parse_tag_3_packet function in fs/ecryptfs/keystore.c in the eCryptfs subsystem in the Linux kernel before 2.6.30.4 allows local users to cause a denial of service (system crash) or possibly gain privileges via vectors involving a crafted eCryptfs file, related to a large encrypted key size in a Tag 3 packet.

The issue has been introduced in 12/25/2008. The weakness was released 07/31/2009 (Website). The advisory is shared at vupen.com. This vulnerability is uniquely identified as CVE-2009-2407 since 07/09/2009. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/13/2021).

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 218 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 43773 (CentOS 5 : kernel (CESA-2009:1193)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165654 (SUSE Enterprise Linux Security Update Linux Kernel (SUSE-SA:2009:045)).

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 (52124), Tenable (43773), SecurityFocus (BID 35850†), Secunia (SA35985†) and Vulnerability Center (SBV-22990†). Entries connected to this vulnerability are available at VDB-46707, VDB-44965, VDB-49049 and VDB-48854. 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: 9.3
VulDB Meta Temp Score: 8.8

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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: 43773
Nessus Name: CentOS 5 : kernel (CESA-2009:1193)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 64555
OpenVAS Name: Debian Security Advisory DSA 1844-1 (linux-2.6.24)
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

12/25/2008 🔍
07/09/2009 +196 days 🔍
07/28/2009 +19 days 🔍
07/28/2009 +0 days 🔍
07/29/2009 +1 days 🔍
07/29/2009 +0 days 🔍
07/31/2009 +2 days 🔍
07/31/2009 +0 days 🔍
03/18/2015 +2056 days 🔍
08/13/2021 +2340 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: vupen.com⛔
Status: Not defined
Confirmation: 🔍

CVE: CVE-2009-2407 (🔍)
GCVE (CVE): GCVE-0-2009-2407
GCVE (VulDB): GCVE-100-49221

OVAL: 🔍

X-Force: 52124
SecurityFocus: 35850 - eCryptfs 'parse_tag_3_packet()' Packet Heap Based Buffer Overflow Vulnerability
Secunia: 35985 - Linux Kernel eCryptfs Two Vulnerabilities, Less Critical
Vulnerability Center: 22990 - Linux Kernel < 2.6.30.4 Heap Based Buffer Overflow Remote Code Execution Vulnerability, Low
Vupen: ADV-2009-2041

See also: 🔍

Entryinfo

Created: 03/18/2015 15:15
Updated: 08/13/2021 09:05
Changes: 03/18/2015 15:15 (63), 02/12/2017 12:58 (15), 08/13/2021 09:05 (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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!