CVE-2018-0818
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 · uneditedMicrosoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".
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 confidenceMicrosoft ChakraCore contains a security feature bypass vulnerability where the scripting engine's memory handling allows an attacker to circumvent Control Flow Guard (CFG), a Windows exploit mitigation. While this vulnerability alone only bypasses a security feature, when combined with another vulnerability it enables arbitrary code execution.
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.
-
Identify if ChakraCore is in useCheck for presence of chakra.dll or chakra.edgedata in the system, or check if applications use ChakraCore as their JavaScript engine (e.g., older Microsoft Edge versions using EdgeHTML, Node.js builds with Chakra support)Affected if ChakraCore/chakra.dll is present on the system or applications relying on ChakraCore are in use
-
Determine ChakraCore versionRight-click on chakra.dll (typically in C:\Windows\System32 or application directories) and view Properties > Details to check the File VersionAffected if All versions of ChakraCore are affected by this CVE; any installed version indicates potential exposure
-
Verify Control Flow Guard (CFG) is enabledRun 'gpedit.msc' and navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options, or use 'Get-ProcessMitigation -PowerShell' to check CFG status for processes using ChakraCoreAffected if CFG is disabled or not enforced - the vulnerability specifically bypasses CFG protection when CFG is present but the bypass is only relevant as a mitigation gap
-
Check for EdgeHTML-based Edge usageOpen Microsoft Edge and navigate to edge://settings/help to confirm the version - older Edge versions using EdgeHTML internally use ChakraCoreAffected if Using legacy Edge (EdgeHTML) rather than Chromium-based Edge, as ChakraCore is embedded in EdgeHTML versions
If ChakraCore is present on the system and CFG is the only mitigating control, the environment is affected by this bypass vulnerability since all ChakraCore versions lack the fix.
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 ChakraCore/Edge as they become available; ensure CFG is enabled system-wide as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0818 — 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-2018-0818 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