CVE-2017-11767
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 · uneditedChakraCore allows an attacker to gain the same user rights as the current user, due to the way that the ChakraCore scripting engine handles objects in memory, 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 confidenceA memory corruption vulnerability in the ChakraCore JavaScript engine allows remote attackers to execute arbitrary code with the same user privileges as the current user by exploiting how the engine handles objects in memory.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Locate ChakraCore.dll on the systemSearch for chakra.dll or ChakraCore.dll in common locations: %ProgramFiles%\Microsoft\Edge\Application, %SystemRoot%\System32, or use 'Get-ChildItem -Path C:\ -Recurse -Filter *chakra*.dll 2>$null' to find all instancesAffected if ChakraCore.dll or chakra.dll is found on the system
-
Identify Microsoft Edge versionOpen Edge, go to Settings > About Microsoft Edge, or run 'msedge --version' from command line, or check the file version of msedge.exe in %ProgramFiles%\Microsoft\Edge\ApplicationAffected if Microsoft Edge is installed (Edge uses ChakraCore as its JavaScript engine)
-
Check for EdgeHTML version if Edge is presentNavigate to edge://settings/help in Edge browser or check the Version registry key at HKLM\SOFTWARE\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}Affected if Microsoft Edge is present - ChakraCore is embedded in Edge
-
Identify applications embedding ChakraCoreReview installed software for applications that may embed ChakraCore (such as Microsoft Office Online, certain Windows features, or custom applications). Check event logs or application documentation.Affected if Any application using ChakraCore as its JavaScript engine is in use
If ChakraCore.dll or Microsoft Edge is present on the system, the environment is affected since all versions of ChakraCore are vulnerable to this memory corruption flaw.
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 for ChakraCore or update to a patched version of Microsoft Edge/EdgeHTML that addresses CVE-2017-11767.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11767 — 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-2017-11767 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