dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 14 Jun 2022.
Internet ExplorerApplication · Microsoft

CVE-2017-0210

HIGH · 8.8 CVSS v3.1 Published 2017-04-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CVE-2017-0210 is an elevation of privilege vulnerability in Internet Explorer where cross-domain policies are not properly enforced. This allows an attacker to inject malicious scripts or access information from one domain and inject it into another domain, bypassing the Same-Origin Policy protection mechanism.

MitigationApply the Microsoft security update (MS17-006) to patch the vulnerability, or migrate to a supported browser such as Microsoft Edge that is not affected by this issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Internet ExplorerApplication
Affected:= 10= 11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Internet Explorer version
    Open Internet Explorer, click the gear icon (Settings), then 'About Internet Explorer' to see the version number
    Affected if Version displayed is 10 or 11
  2. Check if IE is the default browser
    Go to Windows Settings > Default apps > Web browser, or run 'SetDefaultBrowser' command if available, to see which browser is set as default
    Affected if Internet Explorer is set as the default browser and is actively used for web browsing
  3. Identify IE executable presence
    Check for the presence of iexplore.exe in typical locations: C:\Program Files\Internet Explorer\iexplore.exe or C:\Program Files (x86)\Internet Explorer\iexplore.exe
    Affected if The iexplore.exe executable exists on the system
  4. Check for recent IE usage
    Review browser history or enterprise proxy logs to determine if Internet Explorer has been used for web browsing recently
    Affected if Users have accessed websites using Internet Explorer rather than modern Edge or alternative browsers

You are affected if Internet Explorer versions 10 or 11 are installed and users browse the web with IE, enabling the cross-domain policy bypass to be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update (MS17-006) to patch the vulnerability, or migrate to a supported browser such as Microsoft Edge that is not affected by this issue.

Recommended fix High confidence

Apply Microsoft Security Update MS17-013 (March 2017) or later cumulative update. For long-term mitigation, migrate to Microsoft Edge and ensure Windows 10/11 is kept current.

  1. Ensure Windows automatic updates are enabled and allow the system to receive security updates
  2. Run Windows Update to install the latest cumulative security update for your Windows version
  3. If automatic updates are disabled, manually check for updates via Start > Settings > Update & Security > Windows Update > Check for updates
  4. After installing updates, restart the computer as prompted
  5. Alternatively, if Internet Explorer is not required, disable it via Windows Features or migrate to Microsoft Edge
Caveat For organizations still using legacy applications requiring Internet Explorer, test thoroughly before deployment as some legacy ActiveX controls may be affected by security hardening.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0210 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-0210 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data