Hmmm ... says the zero-day cannot currently escape Chrome's sandbox, so it has to work with another vulnerability to turn it off.
I read it's the same bug that was used in Pwn2Own 2021, but I assume they did manage to escape the sandbox. But apparently they used a second hole in either Chrome or Windows to bypass Chrome's sandbox.
I would really like to see a clear explanation on this: they escaped the sandbox with the 2021 Pwn2Own exploit or they didn't.
I don't think they will pay so much for remote code execution without a sandbox escape. I assume when calc.exe is being launched after exploitation, it's runnning with at least medium rights.
Apparently, certain companies were once again being hacked via a Chrome exploit combined with a Windows kernel exploit in order to escape Chrome's sandbox. These type of exploits are almost never being used against home user PC's, but still a good reminder that browsers can still be hacked. So especially companies can use a little bit of extra protection, that's why they often use EDR systems. So if AV's fail to detect malware, behavior monitoring tools should still alert about suspicious behavior. https://securelist.com/puzzlemaker-chrome-zero-day-exploit-chain/102771/
Google has admitted that they are seeing more and more attacks on Chromium based browsers, so it's best to stay alert. Here is some more info about the latest attacks on Chrome via zero days exploits. https://security.googleblog.com/2022/03/whats-up-with-in-wild-exploits-plus.html https://blog.google/threat-analysis-group/countering-threats-north-korea/
