CVE-2018-8266
First published: Wed Aug 15 2018(Updated: )
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8380, CVE-2018-8381, CVE-2018-8384.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| nuget/Microsoft.ChakraCore | <1.10.2 | 1.10.2 |
| Microsoft Chakra | <=1.10.1 | |
| Microsoft Edge Beta | ||
| Microsoft Windows 10 | ||
| Microsoft Windows 10 | =1607 | |
| Microsoft Windows 10 | =1703 | |
| Microsoft Windows 10 | =1709 | |
| Microsoft Windows 10 | =1803 | |
| Microsoft Windows Server 2016 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2018-8266
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8266
- https://github.com/chakra-core/ChakraCore/pull/5596
- https://github.com/chakra-core/ChakraCore/commit/d52c72d247cfe6348ae563c6bb4118aa8c42aabf
- https://web.archive.org/web/20210124194825/http://www.securityfocus.com/bid/104977
- https://web.archive.org/web/20211203061111/http://www.securitytracker.com/id/1041457
- https://github.com/advisories/GHSA-5wrx-85mr-7hrg (Advisory)
- http://www.securityfocus.com/bid/104977
- http://www.securitytracker.com/id/1041457
Frequently Asked Questions
What is the severity of CVE-2018-8266?
CVE-2018-8266 is rated as critical due to its potential for remote code execution.
How do I fix CVE-2018-8266?
To fix CVE-2018-8266, ensure that you update Microsoft Edge and ChakraCore to the latest version.
Which software is affected by CVE-2018-8266?
CVE-2018-8266 affects Microsoft Edge and ChakraCore versions up to 1.10.1.
Can CVE-2018-8266 be exploited without user interaction?
Yes, CVE-2018-8266 can be exploited remotely without requiring user interaction.
Is there a workaround for CVE-2018-8266?
Currently, there are no known effective workarounds for CVE-2018-8266 other than applying the security updates.
- collector/github-advisory-latest
- alias/GHSA-5wrx-85mr-7hrg
- alias/CVE-2018-8266
- collector/github-advisory
- agent/type
- agent/severity
- agent/weakness
- agent/references
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/author
- agent/softwarecombine
- agent/tags
- collector/nvd-cve
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/nuget
- vendor/microsoft
- canonical/microsoft chakra
- version/microsoft chakra/1.10.1
- canonical/microsoft edge beta
- canonical/microsoft windows 10
- version/microsoft windows 10/1607
- version/microsoft windows 10/1703
- version/microsoft windows 10/1709
- version/microsoft windows 10/1803
- canonical/microsoft windows server 2016