CVE-2018-8355Not scoredCWE-787

CVE-2018-8355: Microsoft ChakraCore vulnerability

Microsoft · ChakraCore

Affected: Microsoft ChakraCore · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

67.9%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge. This CVE ID is unique from CVE-2018-8353, CVE-2018-8359, CVE-2018-8371, CVE-2018-8372, CVE-2018-8373, CVE-2018-8385, CVE-2018-8389, CVE-2018-8390.

Affected products3

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Microsoft · ChakraCoreChakraCore
Microsoft · Internet Explorer 11Windows 10 for 32-bit Systems; Windows 10 for x64-based Systems; Windows 10 Version 1607 for 32-bit Systems; Windows 10 Version 1607 for x64-based Systems; Windows 10 Version 1703 for 32-bit Systems; Windows 10 Version 1703 for x64-based Systems and 12 more
Microsoft · Microsoft EdgeWindows 10 for 32-bit Systems; Windows 10 for x64-based Systems; Windows 10 Version 1607 for 32-bit Systems; Windows 10 Version 1607 for x64-based Systems; Windows 10 Version 1703 for 32-bit Systems; Windows 10 Version 1703 for x64-based Systems and 5 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Out-of-bounds Write · Memory Corruption
Vendor: Microsoft
Published: August 2018
Band: Likely to be exploited (10% or more), August 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2018-8355 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.