Threats / Microsoft / CVE-2017-8464
CVE-2017-8464
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Windows Shell in multiple Microsoft Windows versions allows local or remote attackers to execute arbitrary code through crafted .LNK files.
Verdict
Today item — known-exploited.
A critical remote code execution vulnerability in Windows Shell processing of shortcut files. Exploitation requires user interaction or local access but enables full system compromise. Active exploitation in the wild confirms severe practical risk.
CISA KEV Yes · 2022-02-104EPSS 0.88582 (verify live)5Exploit Public PoC6CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10).
Probability (EPSS)
EPSS 0.88582 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1701 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious .LNK file and deliver it via email, removable media, or network share to a target system.
Business
End users receive weaponized files that bypass traditional security controls, enabling initial compromise of corporate endpoints.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
When the target views or accesses the .LNK file through Windows Explorer or file operations, my code executes with the user's privileges.
Business
Attackers gain immediate code execution without requiring user awareness, allowing lateral movement and persistence establishment.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish command and control, deploy secondary payloads, or move laterally across the network using compromised credentials.
Business
Incident response costs, data breach exposure, and operational disruption multiply as the attack spreads beyond initial compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05