Linux Kernel 2.6.16/2.6.17.11 Local Privilege Escalation ⚔ [Disputed]

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Linux Kernel 2.6.16/2.6.17.11. This impacts an unknown function. The manipulation results in Local Privilege Escalation. This vulnerability is cataloged as CVE-2006-4663. There is no exploit available. There is ongoing doubt regarding the real existence of this vulnerability.
Details
A vulnerability classified as problematic has been found in Linux Kernel 2.6.16/2.6.17.11 (Operating System). Affected is an unknown code block. The manipulation with an unknown input leads to a local privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
** DISPUTED ** The source code tar archive of the Linux kernel 2.6.16, 2.6.17.11, and possibly other versions specifies weak permissions (0666 and 0777) for certain files and directories, which might allow local users to insert Trojan horse source code that would be used during the next kernel compilation. NOTE: another researcher disputes the vulnerability, stating that he finds "Not a single world-writable file or directory." CVE analysis as of 20060908 indicates that permissions will only be weak under certain unusual or insecure scenarios.
The issue has been introduced in 03/20/2006. The weakness was shared 09/08/2006 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2006-4663 since 09/08/2006. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 172 days. During that time the estimated underground price was around $5k-$25k. The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.9
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/20/2006 🔍09/08/2006 🔍
09/08/2006 🔍
09/08/2006 🔍
03/12/2015 🔍
01/17/2025 🔍
Sources
Vendor: kernel.orgAdvisory: securityfocus.com⛔
Status: Not defined
Disputed: 🔍
CVE: CVE-2006-4663 (🔍)
GCVE (CVE): GCVE-0-2006-4663
GCVE (VulDB): GCVE-100-32184
Entry
Created: 03/12/2015 15:51Updated: 01/17/2025 15:56
Changes: 03/12/2015 15:51 (46), 04/13/2019 20:47 (2), 08/08/2024 01:07 (17), 01/17/2025 15:56 (11)
Complete: 🔍
Cache ID: 216:C96:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.