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 15 Jun 2022.
Internet ExplorerApplication · Microsoft

CVE-2014-2817

HIGH · 8.8 CVSS v3.1 Published 2014-08-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
Microsoft Internet Explorer 6 through 11 allows remote attackers to gain privileges via a crafted web site, 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 · moderate confidence

Internet Explorer versions 6 through 11 contains an elevation of privilege vulnerability that allows remote attackers to gain elevated privileges via a crafted website. The vulnerability allows an attacker to execute code with higher privileges than normally granted to the user, potentially bypassing security restrictions in the browser context.

MitigationApply Microsoft security updates for CVE-2014-2817, or upgrade to a supported browser version. Organizations should ensure all Internet Explorer installations are patched to the latest cumulative security update.

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:= 6= 7= 8= 9= 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. Confirm Internet Explorer is installed
    Check for IE by attempting to launch 'iexplore.exe' from Command Prompt (type 'iexplore -version' or locate in C:\Program Files\Internet Explorer or C:\Program Files (x86)\Internet Explorer). Alternatively, check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\iexplore.exe
    Affected if IE is not present on the system, this CVE does not apply
  2. Identify the installed Internet Explorer version
    Launch Internet Explorer, then navigate to 'Help' > 'About Internet Explorer' to view the version number, or run 'iexplore -version' from Command Prompt. Version format is typically '6.0', '7.0', '8.0', '9.0', '10.0', or '11.0'
    Affected if The displayed version falls within 6, 7, 8, 9, 10, or 11 (for example, 9.0.8112.16421)
  3. Verify the vulnerability applicability conditions
    This is a client-side elevation of privilege flaw requiring a user to actively visit or be redirected to a specially crafted malicious website while using the affected IE version. Check if users have potential exposure to untrusted web content
    Affected if Users run the affected IE version and have the ability to browse websites, meaning the browser is actively used as a client to access web content

The environment is affected if Internet Explorer versions 6 through 11 are installed and actively used by end users to browse web content, as the vulnerability requires a user to visit a specially crafted malicious website to trigger the elevation of privilege.

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 docs.microsoft.com →
Interim mitigation

Apply Microsoft security updates for CVE-2014-2817, or upgrade to a supported browser version. Organizations should ensure all Internet Explorer installations are patched to the latest cumulative security update.

Recommended fix High confidence
  1. Open Windows Update by clicking the Start button, clicking All Programs, and then clicking Windows Update
  2. Click Check for updates and wait while Windows looks for the latest updates for your computer
  3. If updates are found, click Install updates and restart the computer if required
  4. Alternatively, manually download and install Security Update MS14-037 from Microsoft Update Catalog

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

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2817 — 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-2014-2817 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