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

Microsoft Internet Explorer vulnerability

Internet Explorer information disclosure vulnerability in JavaScript handling allows attackers to detect specific files on a user's computer.

Verdict

Today item — known-exploited.

An attacker can exploit improper JavaScript handling in Internet Explorer to enumerate files on a victim's system, potentially revealing sensitive file paths and system configuration details that inform further attacks.

CISA KEV Yes · 2022-05-243EPSS 0.22088 (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-24).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.22088 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Internet Explorer. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-200 Information Exposure — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-200 · Information ExposureAuthorization / 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 a malicious webpage with JavaScript that probes for the existence of specific files on the target system.
Business
User browsing habits and file system structure become visible to external parties, increasing reconnaissance surface.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I detect which security software, applications, or configuration files exist on the target machine based on file presence.
Business
Attackers gain intelligence to tailor subsequent attacks, reducing their operational cost and increasing success rates.
3

Lateral reach — past segmentation narrative 3

Attacker
I use this information to identify vulnerable or outdated software installations that I can exploit in follow-up attacks.
Business
System compromise risk escalates as attackers combine file detection with known exploits for identified software.
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.