libyal liblnk 20191006 liblnk_location_information.c network_share_name_offset out-of-bounds read
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability classified as critical was found in libyal liblnk 20191006. This vulnerability affects the function
network_share_name_offset of the file liblnk_location_information.c. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-125. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
libyal liblnk 20191006 has a heap-based buffer over-read in the network_share_name_offset>20 code block of liblnk_location_information_read_data in liblnk_location_information.c, a different issue than CVE-2019-17264.
The weakness was disclosed 10/09/2019. This vulnerability was named CVE-2019-17401 since 10/09/2019. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Information disclosure
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
10/09/2019 +0 days 🔍
10/10/2019 +1 days 🔍
09/29/2020 +355 days 🔍
SourcesStatus: Not defined
CVE: CVE-2019-17401 (🔍)
EntryCreated: 10/10/2019 10:48 AM
Updated: 09/29/2020 08:10 PM
Changes: (17) vulnerability_cwe vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a source_cve_assigned source_cve_nvd_summary
Might our Artificial Intelligence support you?
Check our Alexa App!