2455 matches found
CVE-2018-8385
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects Internet Explorer 9, ChakraCore, Internet Explorer 11, Microsoft Edge, Internet Explorer 10. This CVE ...
Privilege escalation
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel DXGKRNL driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Privilege Vulnerability." This affects Windows Server 2016, Windows 10, Windows 10 Servers. This CVE ID is unique from...
Remote code execution
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge. This CVE ID is unique from CVE-2018-8353,...
Remote code execution
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8266, CVE-2018-8381,...
CVE-2018-10662
creationtimestamp| type| source ---|---|--- 2018-07-25 19:52:39+00:00| seen| https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/axissrvparhandrce.rb 2018-07-27 00:00:00+00:00| exploited| https://www.exploit-db.com/exploits/45100 2025-01-23 08:14:00+00:00| seen|...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This is due to a type confusion with hoisted SetConcatStrMultiItemBE instructions in the chakra JIT, which can lead to memory corruption or arbitrary code being executed. This vulnerability affects Microsoft Edge. This CVE ID is differe...
CVE-2018-8291
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge. This CVE ID is unique from CVE-2018-8242,...
Remote code execution
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge. This CVE ID is unique from CVE-2018-8242,...
Remote code execution
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8280, CVE-2018-8286,...
EUVD-2022-5445
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8280, CVE-2018-8290,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because of partial initialization in JITManager.cpp, leading to an out-of-bounds read/write that can cause memory corruption.This CVE ID is different from CVE-2017-11793, CVE-2017-11796, CVE-2017-11798, CVE-2017-11799,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This can happen because of an invalid memory read of outgoing parameters during a bailout when an array destructuring is used for call arguments.This CVE ID is different from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-1179...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because it allows redeferral of functions during byte code generation.This CVE ID is different from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-11797, CVE-2017-11798, CVE-2017-11799, CVE-2017-11800,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution attacks. This can happen because it does not prevent the StackScriptFunction::BoxState::Box from accessing uninitialized pointers. This CVE ID is different from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-11797,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because the application attempts to index a detached ArrayBuffer, leading to a use-after-free that can allow RCE attacks. This CVE ID is different from CVE-2017-11886, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because the scripting engine does not properly handle the objects in memory, causing memory corruption. This CVE ID is different from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because the RemoveEmptyLoopAfterMemOp function in BackwardPass.cpp does not properly insert branches. This CVE ID is different from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution RCE. This happens because it does not have ample InlineCache checks, leading to type confusion which allows an attacker to perform RCE. This CVE ID is different from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893,...
Remote Code Execution (RCE)
microsoft.chakracore is vulnerable to remote code execution. This happens because the SetupLocalVariables function in AsmJsModule.cpp fails to check whether a variable was previously used in the initializer, leading to out-of-bound reads which can allow an attacker to perform RCE. This CVE ID is...
Privilege Escalation
microsoft.chakracore is vulnerable to privilege escalation. This happens because there is a flaw when getting the length property from ScriptFunction in the GetPropertyBuiltIns function of JavascriptGeneratorFunction.cpp.This CVE ID is different from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890...