libyal liblnk liblnk_location_information.c liblnk_location_information_read_data Variable Name out-of-bounds ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libyal liblnk. It has been classified as critical. This impacts the function liblnk_location_information_read_data of the file liblnk_location_information.c. This manipulation as part of Variable Name causes out-of-bounds.
This vulnerability is tracked as CVE-2019-17264. The attack is restricted to local execution. No exploit exists.
There is ongoing doubt regarding the real existence of this vulnerability.
Upgrading the affected component is recommended.
Details
A vulnerability has been found in libyal liblnk (unknown version) and classified as critical. Affected by this vulnerability is the function liblnk_location_information_read_data of the file liblnk_location_information.c. The manipulation as part of a Variable Name 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:
In libyal liblnk before 20191006, liblnk_location_information_read_data in liblnk_location_information.c has a heap-based buffer over-read because an incorrect variable name is used for a certain offset.
The weakness was disclosed 10/06/2019. This vulnerability is known as CVE-2019-17264 since 10/06/2019. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Website
- Product: https://github.com/libyal/liblnk/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
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-boundsCWE: CWE-125 / 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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
10/06/2019 🔍10/06/2019 🔍
10/06/2019 🔍
10/07/2019 🔍
08/05/2024 🔍
Sources
Product: github.comAdvisory: 38
Status: Not defined
Disputed: 🔍
CVE: CVE-2019-17264 (🔍)
GCVE (CVE): GCVE-0-2019-17264
GCVE (VulDB): GCVE-100-142987
Entry
Created: 10/07/2019 07:34Updated: 08/05/2024 05:13
Changes: 10/07/2019 07:34 (38), 09/24/2020 17:00 (17), 01/03/2024 18:07 (4), 08/05/2024 05:13 (17)
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.