CVE-2015-6056
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 · uneditedThe (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption 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 · moderate confidenceMemory corruption vulnerability in the JScript and VBScript scripting engines in Internet Explorer versions 9 through 11 allows remote attackers to achieve arbitrary code execution or cause a denial of service by tricking users into visiting specially crafted malicious web pages that trigger improper memory handling in the scripting engine.
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 versionsall versionsCVSS 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.
-
Verify Internet Explorer versionOpen IE, click Help > About Internet Explorer, or run 'winver' command, or check HKLM\SOFTWARE\Microsoft\Internet Explorer\Version vector in registryAffected if IE version is 9, 10, or 11 (the affected versions)
-
Confirm JScript or VBScript is enabled in IEIn IE, go to Internet Options > Security > Custom Level > Script ActiveX controls and Scripting - verify 'Script ActiveX controls marked safe for scripting' is enabled, or check HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains registry keysAffected if JScript or VBScript execution is enabled in IE security settings (required for exploitation)
-
Locate JScript.dll versionFind jscript.dll in %systemroot%\System32 (or %systemroot%\SysWOW64 for 32-bit on 64-bit), right-click > Properties > Details to see file version, or run 'dir %systemroot%\System32\jscript.dll' in command promptAffected if Any version present on an unpatched system - per CVE data, all JScript versions are affected when unpatched
-
Locate VBScript.dll versionFind vbscript.dll in %systemroot%\System32 (or %systemroot%\SysWOW64), right-click > Properties > Details to see file version, or run 'dir %systemroot%\System32\vbscript.dll' in command promptAffected if Any version present on an unpatched system - per CVE data, all VBScript versions are affected when unpatched
-
Check if security update MS15-112 is installedRun 'wmic qfe list' or check Windows Update history, or verify the patch KB3093983 is listed in installed updates via Control Panel > Programs and Features > View installed updatesAffected if MS15-112 (KB3093983) or a subsequent cumulative IE security update is NOT installed - meaning the system remains vulnerable
User is affected if running IE 9-11 with JScript/VBScript enabled on an unpatched system lacking MS15-112 or subsequent cumulative updates.
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.
dbcve · scopedApply Microsoft security update MS15-112 (or subsequent cumulative IE security updates) to patch the vulnerability; until patched, consider disabling JScript/VBScript execution in IE or using Enhanced Mitigation Experience Toolkit (EMET) / Windows Defender Exploit Guard to reduce exploitability.
Upgrade to Windows 10 with Microsoft Edge (or current supported Windows version with latest IE/Edge)
- Apply Microsoft Security Bulletin MS15-112 (or subsequent cumulative security update for IE) which addresses this scripting engine vulnerability
- Ensure Internet Explorer is updated through Windows Update or manual security update download
- For legacy systems no longer receiving patches, consider upgrading to a supported Windows version with modern Edge browser
- Disable VBScript execution in Internet Explorer as a workaround: Go to Internet Options > Security > Custom Level > Disable 'Active scripting' for VBScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6056 — 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-6056 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