News for hackers. Stuff that matters.

A comment on Chrome zero-day released on GitHub – fixed on V8 but still works on latest. Parent comment

Re:Chrome zero-day released on GitHub – fixed on V8 but stil... by rtpg on Monday April 12, 2021 @10:59PM (#26787683)
The pr adding this says that you need to run chrome with —no-sandbox to get the exploit chain (since they don’t have a sandbox buster right now). Kinda feel like the PR to metasploit is more interesting as a link
[ Parent | on HN ]
Re:Chrome zero-day released on GitHub – fixed on V8 but stil... by moozilla on Monday April 12, 2021 @11:34PM (#26787863)
Couldn't find the PR you're referring to, unless it was this one https://github.com/rapid7/metasploit-framework/pull/15007 which was added by the same author as the OP, but looks like a different exploit as far as I can tell?
[ Parent | on HN ]
Re:Chrome zero-day released on GitHub – fixed on V8 but stil... by rtpg on Tuesday April 13, 2021 @04:54AM (#26789769)
I believe it's the same exploit, check out this reference here [0], and you should see the JS snippet

https://github.com/rapid7/metasploit-framework/pull/15007/fi...

[ Parent | on HN ]
Re:Chrome zero-day released on GitHub – fixed on V8 but stil... by saagarjha on Tuesday April 13, 2021 @05:49AM (#26790143)
The code is somewhat different, although you may have recognized that most JS engine exploits look the same once basic primitives are constructed.
[ Parent | on HN ]