What is the severity of CVE-2018-8380?

CVE-2018-8380 is classified as a critical remote code execution vulnerability.

How do I fix CVE-2018-8380?

To address CVE-2018-8380, users should apply the latest security patches provided by Microsoft for Edge and ChakraCore.

Which products are affected by CVE-2018-8380?

CVE-2018-8380 affects Microsoft Edge and ChakraCore versions up to 1.10.1.

What is the impact of CVE-2018-8380?

Successful exploitation of CVE-2018-8380 allows an attacker to execute arbitrary code on the affected system.

Is there a workaround for CVE-2018-8380?

Currently, there are no known workarounds for CVE-2018-8380 other than applying available security updates.

Vulnerability/
CVE-2018-8380

high

7.6

CWE

787

15/8/2018

13/5/2022

5/8/2024

CVE-2018-8380

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-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	=1803

Remedy

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8380

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-8380?
CVE-2018-8380 is classified as a critical remote code execution vulnerability.
How do I fix CVE-2018-8380?
To address CVE-2018-8380, users should apply the latest security patches provided by Microsoft for Edge and ChakraCore.
Which products are affected by CVE-2018-8380?
CVE-2018-8380 affects Microsoft Edge and ChakraCore versions up to 1.10.1.
What is the impact of CVE-2018-8380?
Successful exploitation of CVE-2018-8380 allows an attacker to execute arbitrary code on the affected system.
Is there a workaround for CVE-2018-8380?
Currently, there are no known workarounds for CVE-2018-8380 other than applying available security updates.

collector/github-advisory-latest
alias/GHSA-rxg4-vw2v-rxm4
alias/CVE-2018-8380
collector/github-advisory
agent/type
agent/references
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/weakness
agent/remedy
agent/description
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/1803

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.