dbcve.org
JscriptApplication · Microsoft

CVE-2015-6136

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
The Microsoft (1) VBScript 5.7 and 5.8 and (2) JScript 5.7 and 5.8 engines, as used in Internet Explorer 8 through 11 and other products, allow remote attackers to execute arbitrary code 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 · high confidence

Memory corruption vulnerability in Microsoft VBScript and JScript scripting engines (versions 5.7 and 5.8) allows remote attackers to achieve arbitrary code execution through malicious web pages rendered in Internet Explorer 8 through 11.

MitigationApply Microsoft security updates to address the scripting engine vulnerability; consider disabling VBScript/JScript execution in Internet Explorer as a temporary workaround if immediate patching is not feasible.

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:= 5.7= 5.8
VbscriptApplication
Affected:= 5.7= 5.8

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. Identify installed JScript version
    Check the file version of jscript.dll in C:\Windows\System32\ (or C:\Windows\SysWOW64\ for 32-bit JScript on 64-bit Windows). Right-click the file, select Properties, and view the Details tab, or run: dir /a C:\Windows\System32\jscript.dll
    Affected if The version listed is 5.7.x or 5.8.x (exactly versions 5.7 or 5.8 as listed in affected versions)
  2. Identify installed VBScript version
    Check the file version of vbscript.dll in C:\Windows\System32\ (or C:\Windows\SysWOW64\ for 32-bit VBScript on 64-bit Windows). Right-click the file, select Properties, and view the Details tab, or run: dir /a C:\Windows\System32\vbscript.dll
    Affected if The version listed is 5.7.x or 5.8.x (exactly versions 5.7 or 5.8 as listed in affected versions)
  3. Verify Internet Explorer scripting configuration
    Open Internet Explorer, go to Internet Options > Security > Custom Level, and review the 'Active scripting' setting under the Security zones (or check via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Security Features)
    Affected if Active scripting is enabled for Internet or Intranet zones, allowing JScript/VBScript to execute in web pages

You are affected if either JScript 5.7/5.8 or VBScript 5.7/5.8 is installed AND Internet Explorer is used with scripting enabled to render untrusted web content.

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 updates to address the scripting engine vulnerability; consider disabling VBScript/JScript execution in Internet Explorer as a temporary workaround if immediate patching is not feasible.

Recommended fix High confidence

Apply Microsoft security update MS15-124 or later cumulative update which includes the fixed scripting engine versions beyond 5.8

  1. Open Windows Update or check for system updates
  2. Apply Microsoft security update MS15-124 (Cumulative Security Update for Internet Explorer) or later cumulative update
  3. Restart the system if prompted
  4. Verify the VBScript version is updated from 5.7/5.8 to a patched version via 'reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup' or check installed updates
Caveat None typical for security updates; this is a routine cumulative security patch

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

Fix this in Jscript Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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