CVE-2015-6078
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 · uneditedMicrosoft Internet Explorer 9 through 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-6065.
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 confidenceMemory corruption vulnerability in Microsoft Internet Explorer 9-11 and Microsoft Edge allows remote attackers to execute arbitrary code via crafted malicious web pages. The vulnerability involves improper memory handling that can be triggered when a user visits a specially designed website, leading to remote code execution or denial of service.
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 dataall versions= 9= 10= 11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Internet Explorer versionOpen Internet Explorer and navigate to 'Help' > 'About Internet Explorer', or check the registry key HKLM\SOFTWARE\Microsoft\Internet Explorer\VersionAffected if The version listed is 9.x, 10.x, or 11.x (exact versions match the affected range)
-
Check Microsoft Edge versionOpen Microsoft Edge and navigate to edge://settings/help, or run 'Get-AppxPackage *Microsoft.Edge* | Select-Object PackageVersion' in PowerShellAffected if Microsoft Edge is installed (all versions of Edge are affected)
-
Verify security update MS15-116 is installedOpen Control Panel > Programs and Features > View installed updates, or run 'Get-HotFix -Id KB3116180' in PowerShell (KB3116180 corresponds to MS15-116)Affected if The update KB3116180 (or a subsequent cumulative update containing this fix) is NOT listed in installed updates
-
Check Windows Update history for cumulative updateOpen Windows Update > View update history, or check for recent Internet Explorer cumulative updates (such as KB3124275 or later)Affected if No Internet Explorer cumulative security updates released after November 2015 are installed
A system is affected if it runs Internet Explorer 9, 10, or 11 OR Microsoft Edge, AND the MS15-116 security update (KB3116180) or a later cumulative update is missing.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Microsoft security update MS15-116 (or subsequent cumulative update) to patch the vulnerability; until patched, restrict user access to untrusted websites and consider enabling Enhanced Mitigation Experience Toolkit (EMET) or Exploit Protection features.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6078 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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