CVE-2017-8669
Last modified
CVE-2017-8669 is a vulnerability of currently unknown severity. Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user due to Microsoft browsers improperly handling objects in memory while rendering content, aka "Microsoft Browser Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8653.. EPSS estimates a 8.47% chance of exploitation in the next 30 days.
Description
Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user due to Microsoft browsers improperly handling objects in memory while rendering content, aka "Microsoft Browser Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8653.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Edge | All versions |
| Microsoft | Internet Explorer | 11 |
References
- http://www.securityfocus.com/bid/100068Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039094Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039095Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8669Patch, Vendor Advisory
- http://www.securityfocus.com/bid/100068Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039094Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039095Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8669Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-8669?
How severe is CVE-2017-8669?
How do I fix CVE-2017-8669?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-8662Microsoft Edge in Microsoft Windows 10 1703 allows an attack…
- CVE-2017-8663Microsoft Outlook 2007 SP3, Outlook 2010 SP2, Outlook 2013 S…
- CVE-2017-8664Windows Hyper-V in Windows 8.1, Windows Server 2012 Gold and…
- CVE-2017-8665The Xamarin.iOS update component on systems running macOS al…
- CVE-2017-8666Microsoft Win32k in Windows Server 2008 SP2 and R2 SP1, Wind…
- CVE-2017-8668The Volume Manager Extension Driver in Microsoft Windows 7 S…
- CVE-2017-8670Microsoft Edge in Microsoft Windows 10 1607, 1703, and Windo…
- CVE-2017-8671Microsoft Edge in Microsoft Windows 10 1511, 1607, 1703, and…
- CVE-2017-8672Microsoft Edge in Microsoft Windows 10 1511, 1607, 1703, and…
- CVE-2017-8673The Remote Desktop Protocol (RDP) implementation in Microsof…
- CVE-2017-8674Microsoft Edge in Microsoft Windows 10 1703 allows an attack…
- CVE-2017-8675The Windows Kernel-Mode Drivers component on Microsoft Windo…
Are you affected by CVE-2017-8669?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
