libfsntfs up to 2018-04-20 ntfs File libfsntfs_attribute.c libfsntfs_attribute_read_from_mft out-of-bounds ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libfsntfs up to 2018-04-20. It has been rated as critical. Impacted is the function libfsntfs_attribute_read_from_mft of the file libfsntfs_attribute.c of the component ntfs File Handler. This manipulation causes out-of-bounds.
This vulnerability is tracked as CVE-2018-11727. The attack is possible to be carried out remotely. No exploit exists.
It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability was found in libfsntfs up to 2018-04-20. It has been declared as critical. Affected by this vulnerability is the function libfsntfs_attribute_read_from_mft of the file libfsntfs_attribute.c of the component ntfs File Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads 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:
The libfsntfs_attribute_read_from_mft function in libfsntfs_attribute.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. NOTE: the vendor has disputed this as described in libyal/libfsntfs issue 8 on GitHub
The bug was discovered 06/06/2018. The weakness was disclosed 06/19/2018 as not defined mailinglist post (Full-Disclosure). It is possible to read the advisory at seclists.org. This vulnerability is known as CVE-2018-11727 since 06/05/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
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-119708, VDB-119709, VDB-119710 and VDB-119711 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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-11727 (🔍)
GCVE (CVE): GCVE-0-2018-11727
GCVE (VulDB): GCVE-100-119707
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:26 (1), 03/28/2023 09:10 (3), 06/05/2024 10:30 (27), 08/05/2024 12:51 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.