CVE-2016-3207
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 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-3206.
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 confidenceMemory corruption vulnerability in Microsoft JScript 5.8 and VBScript 5.7/5.8 scripting engines used in Internet Explorer 9-11 allows remote code execution or denial of service via a maliciously crafted website.
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= 5.8= 5.7= 5.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check JScript versionOpen Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" /s | findstr JScript. This will show installed JScript packages. Alternatively, locate jscript.dll in %systemroot%\System32 and check its file properties for version info.Affected if The JScript version shown is exactly 5.8 (such as 5.8.7600.xxxx)
-
Check VBScript versionOpen Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" /s | findstr VBScript. This will show installed VBScript packages. Alternatively, locate vbscript.dll in %systemroot%\System32 and check its file properties for version info.Affected if The VBScript version shown is exactly 5.7 or 5.8 (such as 5.7.6002.xxxx or 5.8.7600.xxxx)
-
Confirm Internet Explorer 9, 10, or 11 is installedOpen Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version. The Version value will indicate which IE version is installed.Affected if The reported Internet Explorer version starts with 9., 10., or 11.
-
Verify scripting engine is enabled in Internet ExplorerOpen Internet Explorer, go to Internet Options > Security > Custom Level. Scroll to the 'Script ActiveX controls marked safe for scripting' and 'Script ActiveX controls not marked as safe' settings. Also check Tools > Manage Add-ons for JScript and VBScript add-ons.Affected if JScript or VBScript add-ons are enabled in Internet Explorer and scripting is allowed for affected zones.
The system is affected if it runs Internet Explorer 9-11 with JScript 5.8 or VBScript 5.7/5.8 installed and scripting is enabled in the browser.
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.
From vendor dataApply Microsoft security updates for the scripting engine vulnerabilities; consider disabling VBScript/JScript execution in Internet Explorer or using Enhanced Protected Mode as a workaround until patches are applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3207 — 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-2016-3207 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