CVE-2019-17401 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 LNK 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-17401?

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

Official description

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

Weakness: CWE-125

Which versions are affected by CVE-2019-17401?

It affects 1 product.

Products include Liblnk Project Liblnk.

How do I fix CVE-2019-17401?

No fix has been published for CVE-2019-17401 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-17401 being exploited?

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

Sources

Also known as DEBIAN-CVE-2019-17401, GHSA-6hx3-24v8-6q6q.

Is CVE-2019-17401 in your software?

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

Check your SBOMs for free