dbcve.org
JscriptApplication · Microsoft

CVE-2016-3206

HIGH · 7.5 CVSS v3.0 Published 2016-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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) JScript 5.8 and (2) VBScript 5.7 and 5.8 engines, as used in Internet Explorer 9 through 11 and other products, 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," a different vulnerability than CVE-2016-3205 and CVE-2016-3207.

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 Microsoft JScript 5.8 and VBScript 5.7/5.8 scripting engines used in Internet Explorer 9-11 and other products. Attackers can achieve remote code execution or cause denial of service by tricking users into visiting crafted malicious web pages that trigger the memory corruption.

MitigationApply Microsoft security updates for affected scripting engine components; alternatively, disable JScript/VBScript execution in Internet Explorer or restrict Internet Zone activity to minimize attack surface.

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.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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Check installed JScript version
    Run 'cscript //Nologo -e:echo(GetObject('script:\machine\scripting\components\JScript').Version)' or check the jscript.dll version via file properties. Alternatively, query the ScriptEngineVersion build number from within a JScript/VBScript execution context.
    Affected if The JScript version reports as build 5.8.x (version 5800 series) - this matches the affected version = 5.8.
  2. Check installed VBScript version
    Run 'cscript //Nologo -e:echo(GetObject('script:\machine\scripting\components\VBScript').Version)' or check the vbscript.dll version via file properties. Query the ScriptEngineVersion build number from within a VBScript execution context.
    Affected if The VBScript version reports as build 5.7.x or 5.8.x (version 5700 or 5800 series) - this matches the affected versions = 5.7 or = 5.8.
  3. Identify Internet Explorer usage
    Check if Internet Explorer 9, 10, or 11 is installed on the system. Run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' to retrieve the IE version.
    Affected if Internet Explorer versions 9, 10, or 11 are present and the JScript/VBScript versions from checks 1 or 2 are in the affected ranges.
  4. Detect scripting engine DLL file versions
    Locate jscript.dll and vbscript.dll in the system (typically in System32) and view the File Version property. The version numbers correspond to the scripting engine releases.
    Affected if jscript.dll or vbscript.dll versions align with JScript 5.8 or VBScript 5.7/5.8 respectively.

A system is affected if it runs Internet Explorer 9-11 and has JScript version 5.8 or VBScript version 5.7 or 5.8 installed, as these are the specific versions with the memory corruption flaw.

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 updates for affected scripting engine components; alternatively, disable JScript/VBScript execution in Internet Explorer or restrict Internet Zone activity to minimize attack surface.

Fix this in Jscript Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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