Skip to content
Server Security Center
KEVhigh7.5

CVE-2018-8298: ChakraCore Scripting Engine Type Confusion

ChakraCore scripting engine · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.

CVSS v3.1 (CISA ADP)
7.5
high
EPSS (exploit probability, 30 days)
74%
higher than 99.5% of all CVEs
Added to CISA KEV
2022-03-03
US federal due date 2022-03-17
Automatable (CISA SSVC)
no
technical impact: total

CVE-2018-8298 explained

CVE-2018-8298 is a remote code execution vulnerability in the ChakraCore scripting engine, caused by the way it handles objects in memory (a type confusion weakness, CWE-843). CISA lists it as known to be exploited by attackers, which makes patching a priority for any system or application that embeds ChakraCore.

Impact

A remote attacker without privileges can run arbitrary code if a user interacts with attacker-controlled content, such as by loading it in an application using ChakraCore. Attack complexity is high. Successful exploitation fully compromises confidentiality, integrity and availability. CISA rates the technical impact as total and the attack as not automatable. CISA lists the flaw as known to be exploited. Ransomware use is unknown.

Who is affected

The CVE record lists Microsoft ChakraCore as affected. It describes the affected versions only in free text ("ChakraCore") and gives no specific version numbers. The CVE record names no fixed version. Check the vendor advisory to find the update that addresses this vulnerability.

Written with AI from the data on this page and checked against it automatically.

Official description

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 ChakraCore. This CVE ID is unique from CVE-2018-8242, CVE-2018-8283, CVE-2018-8287, CVE-2018-8288, CVE-2018-8291, CVE-2018-8296.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft ChakraCore
    Affected
    • ChakraCore
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-03-17 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the ChakraCore updates per vendor instructions, as CISA requires.
  2. Identify all applications and systems that embed or ship the ChakraCore scripting engine.
  3. Rebuild or update applications that bundle ChakraCore so they include the patched engine.
  4. Limit exposure to untrusted scripts and web content in applications using ChakraCore until patched.
  5. Check affected systems for signs of compromise, since the flaw is known to be exploited.

The CVE record names no fixed version. Follow the vendor advisory to identify the correct update, and apply updates per vendor instructions as CISA requires. Until patched, restrict the processing of untrusted script content by applications that use ChakraCore and watch for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2018-8298

Is CVE-2018-8298 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03, with a US federal due date of 2022-03-17. Whether it has been used in ransomware campaigns is unknown.
Does exploitation require user action?
Yes. The CVSS vector shows that user interaction is required and attack complexity is high, but no privileges are needed and the attack works over the network.
Which version fixes this vulnerability?
The CVE record names no fixed version. Consult the vendor advisory and apply updates per vendor instructions.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.