dbcve.org
EdgeWeb browser · Microsoft

CVE-2015-6064

HIGH · 9.3 CVSS v2.0 Published 2015-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 10 and 11 and Microsoft Edge allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Microsoft Browser Memory Corruption Vulnerability," a different vulnerability than CVE-2015-6084 and CVE-2015-6085.

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 10/11 and Microsoft Edge allowing remote attackers to execute arbitrary code or cause denial of service via a crafted website.

MitigationApply Microsoft security patches (MS15-116 or subsequent cumulative updates) to affected browsers, or disable affected browsers and use alternative browsers until patches can be deployed.

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
EdgeWeb browser
Affected:all versions
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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Identify if Internet Explorer is the active browser
    Open Internet Explorer and check the version by clicking Help > About Internet Explorer, or run 'winver' and look for IE version info
    Affected if The browser is Internet Explorer version 10 or 11
  2. Check Internet Explorer version number
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' or check Help > About Internet Explorer
    Affected if The displayed version is exactly 10.x or 11.x
  3. Identify if Microsoft Edge is installed
    Check for Microsoft Edge by looking in the Start Menu or checking for the Edge shortcut at C:\Users\{username}\Desktop or C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
    Affected if Microsoft Edge is installed and present on the system (all versions are affected)
  4. Determine if security update MS15-116 or a subsequent cumulative update is applied
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" /s | findstr "MSIE"' or check Windows Update history for security update installation dates around November 2015
    Affected if The system shows no evidence of MS15-116 or later cumulative security updates installed after November 2015

You are affected if Internet Explorer 10 or 11 or Microsoft Edge is installed and the system has not received security update MS15-116 or subsequent cumulative updates.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security patches (MS15-116 or subsequent cumulative updates) to affected browsers, or disable affected browsers and use alternative browsers until patches can be deployed.

Recommended fix High confidence

Apply Microsoft security update MS15-116 (November 2015) or subsequent cumulative security updates via Windows Update

  1. Ensure Windows Update is enabled and configured to automatically download and install security updates
  2. Run Windows Update (Start > Settings > Update & Security > Windows Update > Check for updates)
  3. Install all pending security updates, particularly MS15-116 or subsequent cumulative security updates for Internet Explorer
  4. Restart the system if prompted after installing updates
  5. Verify the update was installed by checking Windows Update history for the relevant security patch
Caveat None - this is a routine security patch that does not introduce breaking changes

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

Fix this in Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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