Linux Kernel 4.15.0 ntfs.ko Filesystem Driver ntfs_end_buffer_async_read out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel 4.15.0. This affects the function ntfs_end_buffer_async_read of the component ntfs.ko Filesystem Driver. This manipulation causes out-of-bounds write.
This vulnerability appears as CVE-2018-12930. The attack requires local access. There is no available exploit.
Details
A vulnerability has been found in Linux Kernel 4.15.0 (Operating System) and classified as critical. Affected by this vulnerability is the function ntfs_end_buffer_async_read of the component ntfs.ko Filesystem Driver. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
ntfs_end_buffer_async_read in the ntfs.ko filesystem driver in the Linux kernel 4.15.0 allows attackers to trigger a stack-based out-of-bounds write and cause a denial of service (kernel oops or panic) or possibly have unspecified other impact via a crafted ntfs filesystem.
The bug was discovered 04/12/2018. The weakness was presented 06/28/2018 by arma (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2018-12930 since 06/28/2018. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/29/2023).
The vulnerability was handled as a non-public zero-day exploit for at least 77 days. During that time the estimated underground price was around $0-$5k.
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 SecurityFocus (BID 104588†). See VDB-120072 and VDB-120074 for similar entries. 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: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD 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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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
04/12/2018 🔍06/28/2018 🔍
06/28/2018 🔍
06/28/2018 🔍
06/28/2018 🔍
06/29/2018 🔍
03/29/2023 🔍
Sources
Vendor: kernel.orgAdvisory: RHSA-2019:0641⛔
Researcher: arma
Status: Not defined
CVE: CVE-2018-12930 (🔍)
GCVE (CVE): GCVE-0-2018-12930
GCVE (VulDB): GCVE-100-120073
SecurityFocus: 104588 - Linux Kernel Multiple Memory Corruption Vulnerabilities
See also: 🔍
Entry
Created: 06/29/2018 08:54Updated: 03/29/2023 11:57
Changes: 06/29/2018 08:54 (63), 02/23/2020 08:59 (4), 03/29/2023 11:57 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.