CVE Intelligence
CISA KEV High

CVE-2017-0210 — Microsoft Internet Explorer Privilege Escalation Vulnerability

An elevation of privilege vulnerability exists when Internet Explorer does not properly enforce cross-domain policies, which could allow an attacker to access information from one domain and inject it into another domain, aka "Internet Explorer Elevation of Privilege Vulnerability."

Published Apr 12, 2017 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · May 24, 2022
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 22.3% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 24, 2022
EPSS FIRST
22.33%
ahead of 98% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Internet Explorer
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 14, 2022 — passed 1584 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Internet Explorer).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  6. EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
  7. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Internet Explorer version Internet Explorer 10 and Internet Explorer 11 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Internet Explorer version 10version 11 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.1 High 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
4.3 CVSS 3.0 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Sources disagree significantly and the divergence is under review. Every score is kept with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 24, 2022
Federal deadline
Jun 14, 2022
passed 1584 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 22.33%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before May 24, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/internet explorer
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · microsoft corporation/internet explorer
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 8.8
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    May 23, 2022 · CISA
  • 2017
  • CVE published
    Apr 12, 2017 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

6 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2022-05
what else CISA listed that month

Related CVEs (same products)

  • CVE-2021-27085 Microsoft Internet Explorer Remote Code Execution Vulnerability KEV Mar 11, 2021
  • CVE-2021-26411 Microsoft Internet Explorer Memory Corruption Vulnerability KEV Mar 11, 2021
  • CVE-2020-0878 Microsoft Edge and Internet Explorer Memory Corruption Vulnerability KEV Sep 11, 2020
  • CVE-2020-1380 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Aug 17, 2020
  • CVE-2020-0968 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Apr 15, 2020
  • CVE-2020-0674 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Feb 11, 2020

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2017-0210 is "Microsoft Internet Explorer Privilege Escalation Vulnerability", rated High. It affects Internet Explorer (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 22.33% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.