CVE-2016-3202
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) Chakra JavaScript, (2) JScript, and (3) VBScript engines, as used in Microsoft Internet Explorer 10 and 11 and Microsoft Edge, 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 confidenceMemory corruption vulnerability in Microsoft Chakra JavaScript, JScript, and VBScript scripting engines used in Internet Explorer 10/11 and Microsoft Edge. Attackers can achieve remote code execution or cause denial of service by tricking users into visiting specially crafted malicious websites.
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 dataall versionsall versionsall versionsCVSS 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.
-
Identify Windows version with vulnerable scripting enginesRun 'winver' or check System Properties to determine if Windows version supports Internet Explorer 10/11 or Microsoft Edge (typically Windows 7 SP1 through Windows 10 prior to June 2016 updates)Affected if Windows version includes IE10, IE11, or Microsoft Edge without June 2016 cumulative security updates
-
Verify if MS16-063 security update is installedRun 'wmic qfe list' or check Windows Update history for security update KB3169991 (for IE) or KB3170053 (for Edge)Affected if The security update MS16-063 (KB3169991 for IE, KB3170053 for Edge) is not installed
-
Check Chakra JavaScript engine versionLocate chakra.dll in C:\Windows\System32\ (or C:\Windows\SysWOW64\ for 32-bit on 64-bit) and right-click to view Properties > Details for file versionAffected if Chakra engine DLL version is present and the system lacks the June 2016 cumulative update
-
Check JScript and VBScript engine versionsLocate jscript.dll and vbscript.dll in C:\Windows\System32\ and check their Properties > Details for version informationAffected if JScript or VBScript DLLs are present and the system lacks the MS16-063 patch
-
Confirm presence of attack vector browsersCheck if Internet Explorer 10/11 or Microsoft Edge is installed by looking in Start Menu or C:\Program Files\ (for IE) or C:\Program Files\WindowsApps\ (for Edge)Affected if Internet Explorer 10/11 or Microsoft Edge is installed on an unpatched system
A user is affected if they are running Windows with Internet Explorer 10/11 or Microsoft Edge, and the system is missing the MS16-063 (June 2016) security update KB3169991 for IE or KB3170053 for Edge.
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 (MS16-063 or subsequent relevant patches) to address the scripting engine vulnerability. Until patched, users should avoid untrusted websites and disable ActiveX scripting if possible.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3202 — 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-3202 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