CVE-2017-8657

CVE-2017-8657 affects Microsoft Edge on Windows 10 (versions 1511, 1607, 1703) and Windows Server 2016. The issue is a memory corruption in the browser’s JavaScript engine when rendering objects in memory, allowing remote code execution under the current user. Exploitation is possible via special...

CVE-2017-8670

Microsoft Edge in Microsoft Windows 10 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corrupti...

CVE-2017-8646

Microsoft Edge in Windows 10 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption...

CVE-2017-8644

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to disclose information due to the way that Microsoft Edge handles objects in memory, aka "Microsoft Edge Information Disclosure Vulnerability". This CVE ID is unique from CVE-2017-8652 and...

CVE-2017-8674

Microsoft Edge in Microsoft Windows 10 1703 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID ...

CVE-2017-8662

CVE-2017-8662 is an information-disclosure vulnerability affecting Microsoft Edge in Windows 10 (1703). The flaw stems from how Edge validates strings in specific scenarios, enabling an attacker to disclose information. Public references confirm the relation to Edge information-disclosure issues ...

CVE-2017-8645

Microsoft Edge in Windows 10 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption...

CVE-2017-8655

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine...

CVE-2017-8640

Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory...

CVE-2017-8634

Microsoft Edge in Microsoft Windows 10 1703 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID ...

CVE-2017-8661

Microsoft Edge in Microsoft Windows 10 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way affected Microsoft scripting engines render when handling objects in memory, aka "Microsoft Edge Memory Corruption Vulnerabilit...

CVE-2017-8637

CVE-2017-8637 affects Microsoft Edge on Windows 10 version 1703, describing a security feature bypass of Arbitrary Code Guard (ACG) due to memory access in Edge’s JIT-compiled code. Connected sources detail that the Chakra/JIT server memory handling can process unvalidated loop headers, enabling ...

CVE-2017-8639

CVE-2017-8639 refers to a memory corruption flaw in Microsoft Edge’s scripting engine when rendering objects in memory on Windows 10 (1607/1703) and Windows Server 2016. The issue could allow an attacker to execute arbitrary code in the context of the current user, typically via a web Page that t...

CVE-2017-8671

CVE-2017-8671 describes a remote code execution vulnerability in Microsoft Edge’s scripting engine (Chakra) for Windows 10 1511/1607/1703 and Windows Server 2016. The root cause is memory corruption when handling objects in memory during JavaScript rendering, allowing an attacker to execute arbit...

CVE-2017-8661

CVE-2017-8661 is a remote-code-execution vulnerability in the Microsoft Edge scripting engine and related Windows scripting components. The issue arises from memory handling of objects in memory, allowing an attacker to run arbitrary code in the context of the current user if a user visits a spec...

CVE-2017-8659

CVE-2017-8659 affects Microsoft Edge and Microsoft Internet Explorer on Windows 10 version 1703, due to the Chakra scripting engine not properly handling objects in memory, enabling information disclosure. The vulnerability is documented as a Chakra information disclosure issue with the Edge/IE m...

CVE-2017-8652

CVE-2017-8652 is an information-disclosure/use-after-free vulnerability in Microsoft Edge on Windows 10 Gold/1511/1607/1703 and Windows Server 2016. The connected sources describe it as Edge memory-objects handling in which an attacker could disclose information. The Nessus/plugin notes this CVE ...

CVE-2017-8638

Technical details for CVE-2017-8638 are not provided in the connected documents. The supplied materials describe the issue at a high level but do not specify affected products/versions, root cause, or remediation. Monitor for updates.

CVE-2017-8646

CVE-2017-8646 concerns a remote code execution vulnerability in Microsoft Edge’s scripting engine memory handling. Affected product/variant: Microsoft Edge on Windows 10 (versions 1511, 1607, 1703) and Windows Server 2016, where the JavaScript engine could corrupt memory while rendering objects i...

CVE-2017-8645

CVE-2017-8645 is a remote-code-execution memory-corruption vulnerability in Microsoft Edge’s scripting engine (JavaScript/Chakra). Affected: Windows 10 versions 1511–1703 and Windows Server 2016, via Edge rendering objects in memory. Root cause: memory corruption during rendering of objects in th...