3 ms·
I would imagine the researcher showed a screenshot of the exploit being run on a copy of Chrom{e,ium} where he had disabled parts of the sandbox (that, or he ha
by saurik 6y ago
I would imagine the researcher showed a screenshot of the exploit being run on a copy of Chrom{e,ium} where he had disabled parts of the sandbox (that, or he has a more complex exploit with another maybe-undisclosed sandbox escape).
- r4j0x00 6y agoHey I'm the exploit author, just run "chrome.exe --no-sandbox exploit.html" it will work.
- superjan 6y agoWhat is your motivation of putting it on github? Have you considered selling it to google?
- albntomat0 6y agoThe bug was originally submitted to Google as part of Pwn2Own by two other people. The GitHub POC was built using the patch and regression test by a third person (who you just replied to). While it's been patched in the v8 Javascript engine, that patch has not made it to Chrome (unless you're compiling Chromium from scratch) as part of Chrome's 2 week release process.