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-0149

HIGH · 8.8 CVSS v3.1 Published 2017-03-17
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 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability." This vulnerability is different from those described in CVE-2017-0018 and CVE-2017-0037.

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

Memory corruption vulnerability in Microsoft Internet Explorer 9 through 11 allows remote attackers to execute arbitrary code or cause denial of service via a crafted website. The vulnerability involves memory corruption in the browser's rendering engine, likely a use-after-free or similar memory handling flaw.

MitigationMigrate away from Internet Explorer to modern, supported browsers as IE is deprecated; for legacy systems requiring IE, implement compensating controls such as restricting IE usage, enabling Enhanced Protected Mode, and employing network-based filtering.

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:= 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. Verify Internet Explorer is installed
    Check for IE by looking in the Start Menu, Program Files, or checking the registry key HKLM\SOFTWARE\Microsoft\Internet Explorer for the Version value
    Affected if Internet Explorer version 9, 10, or 11 is present on the system
  2. Confirm the exact IE version installed
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' or open IE and go to Help > About Internet Explorer to read the displayed version number
    Affected if Version shows 9.x, 10.x, or 11.x (exact versions as listed in affected products)
  3. Check if IE is the default or frequently used browser
    Inspect browser default associations or check for recent IE usage in event logs or user profiles
    Affected if IE is set as default browser or has recent usage history indicating the rendering engine is being invoked
  4. Verify security update status
    Check installed updates by running 'Get-HotFix -Description "Security Update" | Where-Object {$_.HotFixID -eq "KB4012204"}' in PowerShell, or view the installed updates list in Control Panel > Programs and Features > View installed updates
    Affected if Security update KB4012204 (or subsequent cumulative updates containing MS17-007) is NOT installed

A system is affected if Internet Explorer version 9, 10, or 11 is installed and the MS17-007 security update (KB4012204) or later cumulative update has not been applied.

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

Migrate away from Internet Explorer to modern, supported browsers as IE is deprecated; for legacy systems requiring IE, implement compensating controls such as restricting IE usage, enabling Enhanced Protected Mode, and employing network-based filtering.

Recommended fix High confidence

Install Microsoft Security Bulletin MS17-003 (Cumulative Security Update for Internet Explorer, KB 4012203) or later

  1. Open Windows Update in Control Panel or Settings
  2. Click 'Check for updates' to ensure you have the latest Windows updates
  3. Install all pending Windows security updates, particularly the Cumulative Security Update for Internet Explorer
  4. After installation, restart the computer if prompted
  5. Verify the update was installed by checking Windows Update history for the relevant security bulletin (e.g., MS17-003)

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

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing8.0 h
  • Review / QA4.0 h
44.0 hours of engineering $7,840
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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