JscriptApplication · Microsoft

CVE-2015-6056

HIGH · 9.3 CVSS v2.0 Published 2015-10-14
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
The (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 confidence

Memory 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.

MitigationApply 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.

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
JscriptApplication
Affected:all versions
VbscriptApplication
Affected:all versions

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. Verify Internet Explorer version
    Open IE, click Help > About Internet Explorer, or run 'winver' command, or check HKLM\SOFTWARE\Microsoft\Internet Explorer\Version vector in registry
    Affected if IE version is 9, 10, or 11 (the affected versions)
  2. Confirm JScript or VBScript is enabled in IE
    In 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 keys
    Affected if JScript or VBScript execution is enabled in IE security settings (required for exploitation)
  3. Locate JScript.dll version
    Find 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 prompt
    Affected if Any version present on an unpatched system - per CVE data, all JScript versions are affected when unpatched
  4. Locate VBScript.dll version
    Find 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 prompt
    Affected if Any version present on an unpatched system - per CVE data, all VBScript versions are affected when unpatched
  5. Check if security update MS15-112 is installed
    Run '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 updates
    Affected 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.

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-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.

Recommended fix Moderate confidence

Upgrade to Windows 10 with Microsoft Edge (or current supported Windows version with latest IE/Edge)

  1. Apply Microsoft Security Bulletin MS15-112 (or subsequent cumulative security update for IE) which addresses this scripting engine vulnerability
  2. Ensure Internet Explorer is updated through Windows Update or manual security update download
  3. For legacy systems no longer receiving patches, consider upgrading to a supported Windows version with modern Edge browser
  4. Disable VBScript execution in Internet Explorer as a workaround: Go to Internet Options > Security > Custom Level > Disable 'Active scripting' for VBScript
Caveat None for security update; legacy VBScript web content may need modernization if fully disabled

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

Fix this in Jscript 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-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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6056 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