CVE-2016-7243
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 Chakra JavaScript scripting engine in Microsoft Edge allows 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-7200, CVE-2016-7201, CVE-2016-7202, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, and CVE-2016-7242.
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 the Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause denial of service via a crafted website with malicious JavaScript.
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 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.
-
Verify Microsoft Edge is installedCheck for the presence of Microsoft Edge by looking for msedge.exe in C:\Program Files (x86)\Microsoft\Edge\Application\ or C:\Program Files\Microsoft\Edge\Application\Affected if Microsoft Edge executable is not found on the system (not affected because Edge is not present)
-
Determine Chakra scripting engine versionOpen Microsoft Edge, navigate to edge://version, and record the Chakra version number displayedAffected if The Chakra version matches the unpatched version range present in Edge before MS16-129 was applied (vulnerable if no patch applied)
-
Check for security update MS16-129Open Windows Update history (Settings > Update & Security > Windows Update > View update history) or run 'wmic qfe list' command and search for KB3202790 (the KB for MS16-129)Affected if KB3202790 (MS16-129) or a subsequent cumulative update is NOT listed as installed (system is likely vulnerable)
-
Verify Edge is not running vulnerable JavaScriptCheck if Enhanced Protected Mode or Enterprise Mode is enabled in Edge settings, which may limit JavaScript exploitabilityAffected if Enhanced Protected Mode is disabled and the system lacks MS16-129 (higher likelihood of successful exploitation)
A system is affected if Microsoft Edge is installed and the MS16-129 security update (KB3202790) or a subsequent cumulative update has not been applied, leaving the Chakra JavaScript engine vulnerable to memory corruption exploits.
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 the Microsoft security update (MS16-129 or subsequent cumulative update) to patch the Chakra scripting engine memory corruption vulnerability in Edge and associated Windows components.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7243 — 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-7243 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