CVE-2018-8381
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-8266, CVE-2018-8380, CVE-2018-8384.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| nuget/Microsoft.ChakraCore | <1.10.2 | 1.10.2 |
| 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-8381
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8381
- https://github.com/chakra-core/ChakraCore/pull/5596
- https://github.com/chakra-core/ChakraCore/commit/1b77d559416116f9719febb7dee3354150277588
- https://github.com/chakra-core/ChakraCore/wiki/Roadmap#v1102
- https://web.archive.org/web/20210124194906/http://www.securityfocus.com/bid/104980
- https://web.archive.org/web/20211203061111/http://www.securitytracker.com/id/1041457
- https://github.com/advisories/GHSA-6gj2-5366-p95v (Advisory)
- http://www.securityfocus.com/bid/104980
- http://www.securitytracker.com/id/1041457
Frequently Asked Questions
What is the severity of CVE-2018-8381?
CVE-2018-8381 has a critical severity rating due to its potential for remote code execution.
How do I fix CVE-2018-8381?
To fix CVE-2018-8381, you should update Microsoft Edge and ChakraCore to the latest version, specifically at least version 1.10.2 for ChakraCore.
Which software is affected by CVE-2018-8381?
CVE-2018-8381 affects Microsoft Edge and versions of ChakraCore up to 1.10.1.
Can CVE-2018-8381 be exploited remotely?
Yes, CVE-2018-8381 can be exploited remotely, allowing attackers to execute arbitrary code.
Is there a workaround for CVE-2018-8381?
There are no known workarounds for CVE-2018-8381; the best mitigation is to apply the security update.
- collector/github-advisory-latest
- alias/GHSA-6gj2-5366-p95v
- alias/CVE-2018-8381
- collector/github-advisory
- agent/references
- agent/type
- agent/severity
- agent/weakness
- 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/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