basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2017-8464
CVE-2017-8464 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-103EPSS 0.90026 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.90026 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 8 reported-exploitation source(s)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.