libfsntfs up to 2018-04-20 ntfs File libfsntfs_mft_entry.c libfsntfs_mft_entry_read_header out-of-bounds ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in libfsntfs up to 2018-04-20. The impacted element is the function libfsntfs_mft_entry_read_header of the file libfsntfs_mft_entry.c of the component ntfs File Handler. Performing a manipulation results in out-of-bounds.
This vulnerability is cataloged as CVE-2018-11729. It is possible to initiate the attack remotely. There is no exploit available.
The existence of this vulnerability is still disputed at present.
Details
A vulnerability classified as critical has been found in libfsntfs up to 2018-04-20. This affects the function libfsntfs_mft_entry_read_header of the file libfsntfs_mft_entry.c of the component ntfs File Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The libfsntfs_mft_entry_read_header function in libfsntfs_mft_entry.c in libfsntfs through 2018-04-20 allows remote attackers to cause an information disclosure (heap-based buffer over-read) via a crafted ntfs file.
The bug was discovered 06/06/2018. The weakness was shared 06/19/2018 as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2018-11729 since 06/05/2018. 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.
The vulnerability was handled as a non-public zero-day exploit for at least 13 days. During that time the estimated underground price was around $0-$5k. 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.
The entries VDB-119707, VDB-119708, VDB-119710 and VDB-119711 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 5.5
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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
06/05/2018 🔍06/06/2018 🔍
06/19/2018 🔍
06/19/2018 🔍
06/20/2018 🔍
08/05/2024 🔍
Sources
Advisory: 148115Status: Not defined
Disputed: 🔍
CVE: CVE-2018-11729 (🔍)
GCVE (CVE): GCVE-0-2018-11729
GCVE (VulDB): GCVE-100-119709
See also: 🔍
Entry
Created: 06/20/2018 13:32Updated: 08/05/2024 12:51
Changes: 06/20/2018 13:32 (59), 02/20/2020 15:28 (1), 03/28/2023 09:13 (3), 08/05/2024 12:51 (28)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.