CVE-2017-0002
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 · uneditedMicrosoft Edge allows remote attackers to bypass the Same Origin Policy via vectors involving the about:blank URL and data: URLs, aka "Microsoft Edge 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 confidenceMicrosoft Edge contains a Same Origin Policy (SOP) bypass vulnerability that allows remote attackers to access content from different origins. The attack vector involves manipulating about:blank URLs in combination with data: URLs, allowing an attacker to violate the browser's security model and potentially steal sensitive cross-origin data or perform actions on behalf of the user.
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 dataall versionsCVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Microsoft Edge is installedOpen Windows Settings > Apps > Apps & features, or run 'Get-AppxPackage *MicrosoftEdge*' in PowerShell to list Edge installationsAffected if Microsoft Edge is found on the system - all versions are affected by this CVE
-
Determine the Microsoft Edge versionLaunch Edge, navigate to edge://settings/help, or run 'Get-AppxPackage *MicrosoftEdge* | Select-Object Name, Version' in PowerShellAffected if Any version number is returned - the CVE states all Edge versions are affected
-
Confirm Edge is the default or used browserCheck Windows default browser settings under Settings > Apps > Default apps, or observe if Edge is actively used for web browsingAffected if Microsoft Edge is set as default or regularly used for browsing - this makes the SOP bypass exploitable in regular use
-
Verify the vulnerable feature is accessibleThe vulnerability involves Edge handling of about:blank frames combined with data: URLs - check if Edge's content process allows navigation between these URL typesAffected if Edge handles about:blank and data: URLs - the CVE indicates this specific URL combination triggers the SOP bypass
If Microsoft Edge is installed and used, the environment is affected since all versions of Edge contain this Same Origin Policy bypass vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Microsoft security updates for CVE-2017-0002 to patch the Edge browser. Until patched, avoid using Microsoft Edge for sensitive operations and consider using an alternative browser.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-0002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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