Linux Kernel 2.6.17/3.12 fbdev arcfb_write memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Linux Kernel 2.6.17/3.12. Impacted is the function arcfb_write in the library fbdev. This manipulation causes memory corruption.
No exploit is available.
Details
A vulnerability has been found in Linux Kernel 2.6.17/3.12 (Operating System) and classified as critical. Affected by this vulnerability is the function arcfb_write in the library fbdev. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 11/10/2013. The weakness was published 11/11/2013 by x90c as XADV-2013003 Linux Kernel fbdev Driver arcfb_write() Overflow as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. The vendor was not involved in the public release. The exploitation appears to be difficult. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/03/2017).
The vulnerability was handled as a non-public zero-day exploit for at least 2704 days. During that time the estimated underground price was around $25k-$100k.
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 vulnerability database at OSVDB (100416†). Additional details are provided at seclists.org. Similar entries are available at VDB-11337 and VDB-11336. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 8.8VulDB Meta Temp Score: 8.5
VulDB Base Score: 8.8
VulDB Temp Score: 8.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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
06/17/2006 🔍11/10/2013 🔍
11/11/2013 🔍
12/03/2013 🔍
09/03/2017 🔍
Sources
Vendor: kernel.orgAdvisory: XADV-2013003 Linux Kernel fbdev Driver arcfb_write() Overflow
Researcher: x90c
Status: Not defined
GCVE (VulDB): GCVE-100-11335
OSVDB: 100416
Misc.: 🔍
See also: 🔍
Entry
Created: 12/03/2013 09:07Updated: 09/03/2017 14:54
Changes: 12/03/2013 09:07 (49), 09/03/2017 14:54 (2)
Complete: 🔍
Committer:
Cache ID: 216:2DD:103
No comments yet. Languages: en.
Please log in to comment.