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

Microsoft Windows vulnerability

A remote code execution vulnerability in Windows GDI component allows attackers to execute arbitrary code by exploiting improper object handling in memory.

Verdict

Today item — known-exploited.

This vulnerability enables unauthenticated remote attackers to achieve system compromise through crafted input targeting the GDI subsystem. Active exploitation in the wild confirms practical threat.

CISA KEV Yes · 2022-05-253EPSS 0.68684 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 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-05-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.68684 — 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
Weakness (CWE)
Mapped to CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-284 · Improper Access ControlAuthorization / access control
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 malicious input designed to trigger improper memory handling in the Windows GDI component.
Business
Systems remain exposed to remote compromise without user interaction or authentication requirements.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the exploit payload through network vectors targeting vulnerable GDI processing routines.
Business
Attack surface spans all Windows systems with GDI enabled, creating enterprise-wide risk.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with the privileges of the affected process once memory corruption succeeds.
Business
Attackers gain operational control sufficient for data exfiltration, lateral movement, or persistent access.
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)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • 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.