CVE-2018-8354
First published: Thu Sep 13 2018(Updated: )
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8391, CVE-2018-8456, CVE-2018-8457, CVE-2018-8459.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| nuget/Microsoft.ChakraCore | <1.11.1 | 1.11.1 |
| ChakraCore | <=1.10.1 | |
| Microsoft Edge Beta | ||
| Windows 10 | ||
| Windows 10 | =1607 | |
| Windows 10 | =1703 | |
| Windows 10 | =1709 | |
| 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-8354
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8354
- https://github.com/chakra-core/ChakraCore/pull/5688
- https://github.com/chakra-core/ChakraCore/commit/5192cdc08a030a580ba15d1d9aa50f81a6d92211
- https://web.archive.org/web/20210124202704/http://www.securityfocus.com/bid/105232
- https://web.archive.org/web/20210517133345/http://www.securitytracker.com/id/1041623
- https://github.com/advisories/GHSA-6g23-fww6-rfrj (Advisory)
- http://www.securityfocus.com/bid/105232
- http://www.securitytracker.com/id/1041623
Frequently Asked Questions
What is the severity of CVE-2018-8354?
CVE-2018-8354 is rated as critical due to its potential for remote code execution.
How do I fix CVE-2018-8354?
To fix CVE-2018-8354, update Microsoft Edge and ChakraCore to the latest versions provided by Microsoft.
Which software is affected by CVE-2018-8354?
CVE-2018-8354 affects Microsoft Edge and versions of ChakraCore up to 1.10.1 inclusive.
Can CVE-2018-8354 be exploited remotely?
Yes, CVE-2018-8354 can be exploited remotely, allowing an attacker to execute arbitrary code.
Is there a workaround for CVE-2018-8354?
There is no specific workaround for CVE-2018-8354, so applying the update is recommended to mitigate the risk.
- collector/github-advisory-latest
- alias/GHSA-6g23-fww6-rfrj
- alias/CVE-2018-8354
- collector/github-advisory
- agent/type
- agent/remedy
- agent/weakness
- agent/severity
- agent/references
- 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/chakracore
- version/chakracore/1.10.1
- canonical/microsoft edge beta
- canonical/windows 10
- version/windows 10/1607
- version/windows 10/1703
- version/windows 10/1709
- version/windows 10/1803
- canonical/microsoft windows server 2016