dbcve.org
JscriptApplication · Microsoft

CVE-2015-6089

HIGH · 9.3 CVSS v2.0 Published 2015-11-11
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 and (2) JScript engines, as used in Internet Explorer 8 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 · high confidence

Memory corruption vulnerability in Microsoft VBScript and JScript scripting engines used by Internet Explorer 8-11 allows remote attackers to achieve arbitrary code execution via crafted malicious web pages, leveraging heap spraying and memory manipulation techniques.

MitigationApply Microsoft security update MS15-124 immediately; alternatively, disable VBScript/JScript execution in Internet Explorer or migrate to Microsoft Edge/other modern browsers.

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. Identify Internet Explorer version in use
    Open Internet Explorer, click Help > About Internet Explorer, or run 'winver' from command prompt to check if version 8, 9, 10, or 11 is installed
    Affected if Internet Explorer versions 8, 9, 10, or 11 are installed on the system
  2. Verify VBScript execution is enabled in Internet Explorer
    Open Internet Options in IE, go to Security tab, click Custom Level, scroll to 'Script ActiveX controls marked safe for scripting' and 'Active scripting' settings, or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones for zone-based script execution settings
    Affected if VBScript execution is allowed in any IE security zone (particularly Internet and Intranet zones)
  3. Verify JScript execution is enabled in Internet Explorer
    Check the same Active scripting settings in IE Security zones, or inspect registry under HKCU\Software\Microsoft\Windows\ScriptHost\ and HKLM\SOFTWARE\Microsoft\ScriptEngine for JScript configuration
    Affected if JScript execution is allowed in any IE security zone (particularly Internet and Intranet zones)
  4. Confirm VBScript DLL is present on the system
    Check for vbscript.dll location at C:\Windows\System32\vbscript.dll or C:\Windows\SysWOW64\vbscript.dll (32-bit on 64-bit OS), right-click the file and view Properties > Details to see version
    Affected if vbscript.dll exists and is used by Internet Explorer for VBScript processing
  5. Confirm JScript DLL is present on the system
    Check for jscript.dll location at C:\Windows\System32\jscript.dll or C:\Windows\SysWOW64\jscript.dll (32-bit on 64-bit OS), right-click the file and view Properties > Details to see version
    Affected if jscript.dll exists and is used by Internet Explorer for JScript processing
  6. Determine if Internet Explorer is the primary or regularly used browser
    Check default browser settings in Windows (Settings > Apps > Default apps > Web browser), or ask users if they browse the web with Internet Explorer
    Affected if Internet Explorer is set as default browser or is regularly used for web browsing, especially for untrusted sites

The system is affected if Internet Explorer 8-11 is installed and VBScript or JScript execution is enabled in any IE security zone, and the user browses untrusted web content with Internet Explorer.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security update MS15-124 immediately; alternatively, disable VBScript/JScript execution in Internet Explorer or migrate to Microsoft Edge/other modern browsers.

Fix this in Jscript Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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