CVE-2019-17264

Exp

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

Published: 2019-10-06 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-17264 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.43%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-17264

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-17264

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.43% +0.38%
2 2025-03-17 0.04% 0.06% +0.01%
3 2023-03-07 — 0.04% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-17264

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2019-17264

OS Trackers for CVE-2019-17264

vendor priority summary link
debian unimportant CVE-2019-17264 unimportant priority: Debian including 1 source packages (liblnk), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2019-17264
ubuntu medium CVE-2019-17264 medium priority: Ubuntu including 1 source packages (liblnk), 15 status rows across 15 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): ignored 8, not-affected 5, DNE 1, needs-triage 1. https://ubuntu.com/security/CVE-2019-17264

Affected software / configurations for CVE-2019-17264

Vendor Product Version Raw CPE
liblnk_project liblnk < 20191006 cpe:2.3:a:liblnk_project:liblnk:*:*:*:*:*:*:*:*

References for CVE-2019-17264

URL Tags
https://github.com/libyal/liblnk/compare/20181227...20191006 Patch Third Party Advisory
https://github.com/libyal/liblnk/issues/38 Exploit Third Party Advisory
cvelogic Threat Intelligence