CVE-2019-17401: libyal liblnk 20191006 has a heap-based buffer over-read in the network_share_name_offset>20 code block of lib

Routine

LOW 3.3DOWNGRADE

CVE-2019-17401 is a low-severity flaw (CVSS 3.3) affecting liblnk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-125
Published	2019-10-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: liblnk project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-10-09 19:15 UTCPublished CVE record published
2026-06-17 02:23 UTCUpdated Record last modified

liblnk project liblnk DOWNGRADE

Affected: 20191006

Fixed in: no fixed release known

Safe to downgrade to: a release before 20191006

1. Check installed version

apt-cache policy liblnk || rpm -q liblnk || liblnk --version

2. No fixed release: DOWNGRADE to a release before 20191006 (Debian / Ubuntu)

apt-cache madison liblnk sudo apt install liblnk=<VERSION_BEFORE_20191006> sudo apt-mark hold liblnk

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list liblnk sudo dnf downgrade liblnk-<VERSION_BEFORE_20191006> sudo dnf versionlock add liblnk

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-17401?

liblnk: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-17401 being exploited?

CVE-2019-17401 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-17401 affect?

CVE-2019-17401 affects liblnk. Severity is low (CVSS 3.3). 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 d

How urgent is CVE-2019-17401?

Priority 25/100. Public exploit reference

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2019-17264 LOW 3.3 UPGRADE In libyal liblnk before 20191006, liblnk_location_information_read_data in liblnk_location_information.c has a
CVE-2018-12098 MEDIUM 5.5 UPGRADE The liblnk_data_block_read function in liblnk_data_block.c in liblnk through 2018-04-19 allows remote attacker
CVE-2018-12097 MEDIUM 5.5 UPGRADE The liblnk_location_information_read_data function in liblnk_location_information.c in liblnk through 2018-04-
CVE-2018-12096 MEDIUM 5.5 UPGRADE The liblnk_data_string_get_utf8_string_size function in liblnk_data_string.c in liblnk through 2018-04-19 allo

References

← Back to latest CVEs