dbcve.org
EdgeWeb browser · Microsoft

CVE-2015-6139

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 mishandle content types, which allows remote attackers to execute arbitrary web script in a privileged context via a crafted web site, aka "Microsoft Browser 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 · high confidence

A content type handling flaw in Internet Explorer 11 and Microsoft Edge allows attackers to execute arbitrary JavaScript in a privileged browser context (such as the Local Machine zone or another origin) by tricking the browser into misinterpreting the content type of a crafted webpage, effectively achieving elevation of privilege through cross-site scripting.

MitigationDeploy the Microsoft security update (MS15-116 or subsequent patches) to all affected systems running Internet Explorer 11 or Microsoft Edge; verify browser functionality post-patch.

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 Internet Explorer 11 version
    Open Internet Explorer 11, click the gear icon (Tools), select About Internet Explorer, and note the version number displayed in the dialog box
    Affected if Version is 11.0.9600.18125 or lower (pre-MS15-116 patch)
  2. Check Microsoft Edge version
    Open Microsoft Edge, click the three-dot menu, select Settings, scroll down and click About Microsoft Edge to view the version
    Affected if Any version of Microsoft Edge is installed (all versions affected per CVE) and the MS15-116 update has not been applied
  3. Verify MS15-116 security update is installed
    Open Control Panel, go to Programs and Features, click View installed updates, and search for security update KB3116184 (MS15-116) in the list
    Affected if The KB3116184 update is NOT present in the installed updates list
  4. Check Windows version and patch level via systeminfo
    Open Command Prompt and run systeminfo | findstr /C:"KB" to list installed hotfixes, look for KB3116184
    Affected if KB3116184 is not listed among installed hotfixes

The system is affected if running Internet Explorer 11 (any version up to 11.0.9600.18125) or any Microsoft Edge version AND the MS15-116 security update (KB3116184) has not been 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

Deploy the Microsoft security update (MS15-116 or subsequent patches) to all affected systems running Internet Explorer 11 or Microsoft Edge; verify browser functionality post-patch.

Recommended fix High confidence

December 2015 Security Updates (MS15-124) - Internet Explorer 11 and Microsoft Edge

  1. Open Windows Update by clicking the Start button, searching for 'Check for updates', and selecting 'Check for updates'
  2. Click 'Install updates' if updates are available, or ensure automatic updates are enabled
  3. For Internet Explorer 11: Install the December 2015 security update (KB3116180) from MS15-124
  4. For Microsoft Edge: Install the December 2015 security update (KB3116184) from MS15-124
  5. Restart the computer after installing updates
  6. Verify the browser version shows the security update applied

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-6139 — 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-6139 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