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...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to a Use-After-Free UAF vulnerability in JavascriptError::SetErrorMessageProperties which could cause memory corruption and allow an attacker to execute code in the context of the current user. This CVE ID is different from...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to an incorrect scope handling during the emitting of byte code which could cause memory corruption and allow an attacker to execute code in the context of the current user. This CVE ID is different from CVE-2018-0758,...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. The scripting engine does not properly handle the objects in memory, causing memory corruption which could allow an attacker to execute code in the context of the current user. This CVE ID is different from CVE-2018-0758, CVE-2018-0762,...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. It exists because the CreateLabel function in IRBuilderAsmJs.cpp, does not properly check instrPrevparameter, causing memory corruption which allows attacker to trigger RCE. This CVE ID is different from CVE-2017-11886, CVE-2017-11889,...

Information Disclosure

microsoft.chakracore is affected by an information disclosure vulnerability. The application discloses the contents of its memory due to an out-of-bound read, leading to memory corruption. This CVE ID is different from CVE-2018-0767 and CVE-2018-0800...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to a NULL-pointer derefence which could lead to memory corruption and allow an attacker to execute arbitrary code. This CVE ID is different from CVE-2018-0946, CVE-2018-0951, CVE-2018-0953, CVE-2018-0954, CVE-2018-0955,...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to a Use-After-Free UAF vulnerability in ServerScriptContext which could lead to memory corruption and allow an attacker to execute arbitrary code in the context of the authenticated user. This CVE ID is different from...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to a type confusion vulnerability in Chakra JIT which could lead to memory corruption and allow an attacker to execute arbitrary code in the context of the authenticated user. This CVE ID is different from CVE-2018-0945,...

Remote Code Execution (RCE)

microsoft.chakracore is vulnerable to remote code execution. This is due to a Use-After-Free UAF vulnerability in a stack variable which could lead to memory corruption and allow an attacker to execute arbitrary code in the context of the authenticated user. This CVE ID is different from...

Security Advisory - DoS Vulnerability in SMS Module of Some Huawei Smart Phones

There is a Denial of Service DoS vulnerability in the Short Message Service SMS module of some Huawei smart phones. An unauthenticated attacker may set up a pseudo base station, and send special malware text message to the phone, causing the mobile phone to fail to make calls and send and receive...