Re:iLeakage: Browser-Based Timerless Speculative Execution A...
by drvdevd on Wednesday October 25, 2023 @02:15PM
(#38016199)
From a cursory review of the FAQs on the page it appears one mitigation might be to only keep one browser tab open at a time? They appear to be using timers and a cache eviction gadget to infer the state of other browser tabs/processes so it’s unclear what they can recover if you are not concurrently having a session to a particular site outside the gadget execution context. ???
[ Parent
| on HN ]
Re:iLeakage: Browser-Based Timerless Speculative Execution A...
by lights0123 on Wednesday October 25, 2023 @03:03PM
(#38016868)
They use window.open on a mouseover event listener to open another page. Even if you close it, they still are able to read from it as that memory isn't immediately zeroed or returned to the OS.
Re:iLeakage: Browser-Based Timerless Speculative Execution A...
by missblit on Wednesday October 25, 2023 @09:40PM
(#38020695)
Besides windows.open I'd wonder if iframes could also be vulnerable if they launch in the same process.
Chrome and Firefox both support Out-Of-Process Iframes as part of their security setup. (Firefox even drew some lovely pictures about it here: https://hacks.mozilla.org/2021/05/introducing-firefox-new-si... )