CVE-2019-17264 Memory corruption in n/a

Low 3.3 Published Updated

A heap-based buffer over-read in liblnk allows attackers to cause denial of service or disclose sensitive memory contents via crafted files.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2019-17264?

CVE-2019-17264 is a low-severity memory corruption vulnerability in n/a, published on 6 Oct 2019. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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

Weakness: CWE-682, CWE-125

Which versions are affected by CVE-2019-17264?

It affects 1 product.

Products include Liblnk Project Liblnk.

How do I fix CVE-2019-17264?

No fix has been published for CVE-2019-17264 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2019-17264 being exploited?

There is no known exploitation of CVE-2019-17264 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2019-17264, GHSA-qvh2-jh54-687w.

Is CVE-2019-17264 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free