Microsoft ChakraCore vulnerabilities

255 CVEs affecting Microsoft ChakraCore, 2 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2023-37143, published 2023-07-18.

More from Microsoft.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

• CVE-2018-8298: ChakraCore Scripting Engine Type Confusion Vulnerability, published 2018-07-11. High severity, CVSS 7.5. Actively exploited: in CISA KEV since 2022-03-03. EPSS: 74.7% chance of exploitation in the next 30 days. A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects…
• CVE-2020-0878: Microsoft Edge and Internet Explorer Memory Corruption Vulnerability, published 2020-09-11. Medium severity, CVSS 4.2. Actively exploited: in CISA KEV since 2021-11-03. EPSS: 2.7% chance of exploitation in the next 30 days. <p>A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory. The vulnerability could corrupt memory in a way that could allow an attacker to execute…
• CVE-2019-0539, published 2019-01-08. High severity, CVSS 7.5. EPSS: 82.9% chance of exploitation in the next 30 days. 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."…
• CVE-2018-0758, published 2018-01-04. High severity, CVSS 7.5. EPSS: 80.8% chance of exploitation in the next 30 days. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine…
• CVE-2019-0567, published 2019-01-08. High severity, CVSS 7.5. EPSS: 80.1% chance of exploitation in the next 30 days. 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."…
• CVE-2018-0769, published 2018-01-04. High severity, CVSS 7.5. EPSS: 79% chance of exploitation in the next 30 days. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine…
• CVE-2018-0777, published 2018-01-04. High severity, CVSS 7.5. EPSS: 78.4% chance of exploitation in the next 30 days. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine…
• CVE-2018-0776, published 2018-01-04. High severity, CVSS 7.5. EPSS: 78.4% chance of exploitation in the next 30 days. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine…
• CVE-2018-0770, published 2018-01-04. High severity, CVSS 7.5. EPSS: 78.4% chance of exploitation in the next 30 days. Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine…
• CVE-2018-8229, published 2018-06-14. High severity, CVSS 7.5. EPSS: 71% chance of exploitation in the next 30 days. 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."…

Latest

• CVE-2023-37143, published 2023-07-18. Medium severity, CVSS 5.5. EPSS: 0.8% chance of exploitation in the next 30 days. ChakraCore branch master cbb9b was discovered to contain a segmentation violation via the function BackwardPass::IsEmptyLoopAfterMemOp().
• CVE-2023-37142, published 2023-07-18. Medium severity, CVSS 5.5. EPSS: 0.8% chance of exploitation in the next 30 days. ChakraCore branch master cbb9b was discovered to contain a segmentation violation via the function Js::EntryPointInfo::HasInlinees().
• CVE-2023-37141, published 2023-07-18. Medium severity, CVSS 5.5. EPSS: 0.8% chance of exploitation in the next 30 days. ChakraCore branch master cbb9b was discovered to contain a segmentation violation via the function Js::ProfilingHelpers::ProfiledNewScArray().
• CVE-2023-37140, published 2023-07-18. Medium severity, CVSS 5.5. EPSS: 0.8% chance of exploitation in the next 30 days. ChakraCore branch master cbb9b was discovered to contain a segmentation violation via the function Js::DiagScopeVariablesWalker::GetChildrenCount().
• CVE-2023-37139, published 2023-07-18. Medium severity, CVSS 5.5. EPSS: 0.9% chance of exploitation in the next 30 days. ChakraCore branch master cbb9b was discovered to contain a stack overflow vulnerability via the function Js::ScopeSlots::IsDebuggerScopeSlotArray().
• CVE-2020-23315, published 2022-01-20. High severity, CVSS 7.5. EPSS: 2.4% chance of exploitation in the next 30 days. There is an ASSERTION (pFuncBody->GetYieldRegister() == oldYieldRegister) failed in Js::DebugContext::RundownSourcesAndReparse in ChakraCore version 1.12.0.0-beta.
• CVE-2020-17131, published 2020-12-10. Medium severity, CVSS 4.2. EPSS: 2% chance of exploitation in the next 30 days. Chakra Scripting Engine Memory Corruption Vulnerability
• CVE-2020-17054, published 2020-11-11. Medium severity, CVSS 4.2. EPSS: 2.1% chance of exploitation in the next 30 days. Chakra Scripting Engine Memory Corruption Vulnerability
• CVE-2020-17048, published 2020-11-11. Medium severity, CVSS 4.2. EPSS: 1.6% chance of exploitation in the next 30 days. Chakra Scripting Engine Memory Corruption Vulnerability
• CVE-2020-1180, published 2020-09-11. Medium severity, CVSS 4.2. EPSS: 2.1% chance of exploitation in the next 30 days. <p>A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory. The vulnerability could corrupt memory in such a way that an attacker could…