Threats / Microsoft / CVE-2019-0752
CVE-2019-0752
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Internet Explorer vulnerability
Remote code execution vulnerability in Internet Explorer's scripting engine memory handling. Exploited in the wild with ransomware campaigns.
Verdict
Today item, not a backlog item.
A memory corruption flaw in Internet Explorer's script processing enables unauthenticated remote code execution. High EPSS score and active exploitation in ransomware operations indicate significant real-world risk.
CISA KEV Yes · 2022-02-154Ransomware use Flagged4EPSS 0.81551 (verify live)5Exploit Public PoC6CVSS 7.5 (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
2 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-15), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.81551 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Microsoft, Internet Explorer. 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.
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
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 1043 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.
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
Craft malicious webpage or email with specially formatted script to trigger memory corruption in IE scripting engine
Business
User visits compromised or attacker-controlled website, triggering automatic code execution without user interaction
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Execute arbitrary code with privileges of the browsing user to establish persistence and lateral movement
Business
Attacker gains foothold on corporate network, enabling data exfiltration and further compromise
3
Lateral reach — past segmentation narrative 3
Attacker
Deploy ransomware payload across compromised systems and connected infrastructure
Business
Critical business systems encrypted, operations halted, ransom demanded, regulatory and reputational damage
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