Cyber Resilience

CVE-2018-8298

Memory Safety in Microsoft Chakracore ≤ 1.10.1

CISA KEVActive ExploitationEUVD ExploitedPublic PoCMemory Safety
Published
11 July 2018
Modified
28 October 2025
KEV Added
03 March 2022
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.75 99.5th percentile
Risk Priority 82 floored blend · peak EPSS

Summary

CVE-2018-8298 is a high-severity Type Confusion (CWE-843) vulnerability in Microsoft Chakracore. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.5% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, resulting in memory corruption classified under CWE-843. This affects ChakraCore and is tracked separately from multiple related issues in the same engine.

An attacker can exploit the flaw over a network with no privileges required but high attack complexity and user interaction needed, achieving high-impact effects on confidentiality, integrity, and availability.

Microsoft Security Response Center advisories reference the issue for guidance, while public exploit code is listed on Exploit-DB. The CVSS 7.5 score reflects the remote attack surface and potential for full system compromise when triggered.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-843
KEV Date Added
03 March 2022

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38178Same vendor: Microsoftboth on KEV
CVE-2019-0752Same vendor: Microsoftboth on KEV
CVE-2017-0037Same vendor: Microsoftboth on KEV
CVE-2016-7201Same vendor: Microsoftboth on KEV
CVE-2022-41033Same vendor: Microsoftboth on KEV
CVE-2025-30397Same vendor: Microsoftboth on KEV
CVE-2026-21519Same vendor: Microsoftboth on KEV
CVE-2023-37139Same product: Microsoft Chakracore
CVE-2024-7971Same vendor: Microsoftboth on KEV
CVE-2025-53726Same vendor: Microsoft

Affected Assets

microsoft
chakracore
≤ 1.10.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References