dbcve.org
EdgeWeb browser · Microsoft

CVE-2015-6153

HIGH · 9.3 CVSS v2.0 Published 2015-12-09
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-6140, CVE-2015-6142, CVE-2015-6143, CVE-2015-6158, CVE-2015-6159, and CVE-2015-6160.

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 allowing remote attackers to execute arbitrary code or cause denial of service via a crafted website. This is a client-side browser vulnerability in the rendering engine.

MitigationApply Microsoft security update MS15-124 (or subsequent cumulative update for IE/Edge). Until patched, restrict browsing to trusted sites only and consider alternative browsers.

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. Check if Microsoft Edge is installed
    Open Settings > Apps > Apps & features, or run 'Get-AppxPackage *Microsoft.Edge*' in PowerShell. Alternatively, check for msedge.exe in Program Files or Program Files (x86).
    Affected if Microsoft Edge is present on the system (all versions are affected before patching)
  2. Check if Internet Explorer 11 is installed
    Open Internet Explorer, go to Help > About Internet Explorer. Alternatively, check the registry key HKLM\SOFTWARE\Microsoft\Internet Explorer for the Version value.
    Affected if Internet Explorer 11 is present (this version is in the affected range)
  3. Determine the exact Internet Explorer version
    In IE, open Help > About Internet Explorer and note the version string (e.g., 11.0.9600.xxxxx). Compare this against the affected version 11.
    Affected if The version shows 11.x (any subversion of IE 11 is affected before MS15-124)
  4. Check if the security update is applied
    Open Windows Update > View update history, or check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages for installed security updates. Look for entries containing 'MS15-124' or cumulative IE updates from December 2015 or later.
    Affected if The MS15-124 security update or subsequent cumulative IE updates are NOT installed (system is vulnerable)
  5. Verify the rendering engine version (alternative method)
    In Internet Explorer, open Developer Tools (F12) and check the Trident engine version, or check the file version of mshtml.dll in System32 (right-click > Properties > Details).
    Affected if The mshtml.dll version is older than the version shipped with MS15-124 (pre-December 2015)

A system is affected if it runs Microsoft Edge of any version, or Internet Explorer 11, and does not have security update MS15-124 or a subsequent cumulative update installed.

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 update MS15-124 (or subsequent cumulative update for IE/Edge). Until patched, restrict browsing to trusted sites only and consider alternative browsers.

Recommended fix High confidence

Install Microsoft security update MS15-124 (December 2015 Cumulative Security Update for Internet Explorer)

  1. Apply the December 2015 security update (MS15-124) from Microsoft which addresses CVE-2015-6153
  2. Install the update via Windows Update: Start > Settings > Update & Security > Windows Update > Check for updates
  3. Alternatively, download the update manually from the Microsoft Security Bulletin MS15-124 page on docs.microsoft.com
  4. Restart the computer after installing the update
  5. Verify the update is installed by checking Windows Update history

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

Fix this in Edge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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