dbcve.org
EdgeWeb browser · Microsoft

CVE-2015-6073

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 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-6068, CVE-2015-6072, CVE-2015-6075, CVE-2015-6077, CVE-2015-6079, CVE-2015-6080, and CVE-2015-6082.

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 11 and Microsoft Edge allows remote attackers to execute arbitrary code or cause denial of service via a crafted malicious website. The vulnerability stems from improper memory handling in the browsers' rendering engine.

MitigationApply Microsoft security updates for affected browsers (IE11 and Edge) or upgrade to patched versions. Until patched, restrict user access to untrusted websites and disable unnecessary browser extensions.

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:= 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 Internet Explorer version
    Open IE11, click the gear icon (Settings), then select 'About Internet Explorer'. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Version
    Affected if The displayed version is 11 and the system lacks the security update for this CVE
  2. Identify Microsoft Edge version
    Open Microsoft Edge, navigate to edge://settings/help, or use PowerShell: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe' | Select-Object -ExpandProperty Version
    Affected if Edge is installed and the version predates the November 2015 security updates
  3. Verify security update installation
    Open Control Panel > Programs and Features > View installed updates. Look for MS15-112 or related security updates for IE/Edge released in November 2015
    Affected if No relevant security update from November 2015 or later is listed for Internet Explorer or Edge
  4. Confirm browser exposure
    Check if the browser is used to access untrusted websites. Review browser security zone settings under Internet Options > Security
    Affected if The browser regularly accesses untrusted web content without additional filtering or protection

A user is affected if they run Internet Explorer 11 or any version of Microsoft Edge without the November 2015 security patches installed, particularly if they browse untrusted websites.

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 updates for affected browsers (IE11 and Edge) or upgrade to patched versions. Until patched, restrict user access to untrusted websites and disable unnecessary browser extensions.

Recommended fix High confidence

Modern Chromium-based Microsoft Edge (for end-of-life legacy Edge/IE11 systems)

  1. Apply Microsoft security update MS15-112, which addresses this vulnerability in Internet Explorer 11 and Microsoft Edge.
  2. On Windows 10 systems, install the November 2015 cumulative security update (KB3103688) through Windows Update or Microsoft Update Catalog.
  3. Verify the update was successfully installed by checking Windows Update history.
  4. For systems running legacy Edge or IE11 beyond support lifecycle, migrate to the modern Chromium-based Microsoft Edge browser.
  5. Ensure Windows Defender or your antivirus is up to date as an additional layer of defense until patching is complete.
Caveat Legacy Edge and IE11 are end-of-life; migrating to Chromium Edge may require adjusting compatibility settings for legacy web applications.

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

Fix this in Edge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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