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

Microsoft Internet Explorer vulnerability

Microsoft Internet Explorer Scripting Engine memory corruption vulnerability enabling remote code execution through malformed objects.

Verdict

Today item — known-exploited.

A memory corruption flaw in Internet Explorer's Scripting Engine allows attackers to execute arbitrary code remotely. The vulnerability has been observed in active exploitation. CWE-787 indicates out-of-bounds write conditions.

CISA KEV Yes · 2021-11-033EPSS 0.2911 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.2911 — 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-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
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 or document containing specially formed script objects designed to trigger memory corruption in the target's Internet Explorer instance.
Business
Users visiting untrusted or compromised websites face immediate risk of system compromise and unauthorized code execution.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I trigger the vulnerability by inducing the Scripting Engine to mishandle object references, causing an out-of-bounds memory write that overwrites critical process memory.
Business
Attackers gain execution context within the browser process, potentially escalating to full system compromise depending on user privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with the privileges of the affected user, establishing persistence or lateral movement within the target environment.
Business
Organizations face data theft, malware installation, and operational disruption across affected endpoints.
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)
  • 5 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.