CVE-2019-17264

Public Exploit

Description

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. NOTE: the vendor has disputed this as described in the GitHub issue

Category

3.3
CVSS
Severity: Low
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.06%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/libyal/liblnk/issues/38 third party advisory exploit
https://github.com/libyal/liblnk/compare/20181227...20191006 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2019-17264?
CVE-2019-17264 has been scored as a low severity vulnerability.
How to fix CVE-2019-17264?
To fix CVE-2019-17264, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-17264 being actively exploited in the wild?
It is possible that CVE-2019-17264 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.