3 ms·
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 lik
by rtpg 6y ago
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
- moozilla 6y agoCouldn't find the PR you're referring to, unless it was this one https://github.com/rapid7/metasploit-framework/pull/15007 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?
- rtpg 6y agoI 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/files#diff-42ae645fcacbd90d93296471ac57e1d734544af7fb082efd607db0a29d197ac4R53 https://github.com/rapid7/metasploit-framework/pull/15007/fi...
- saagarjha 6y agoThe code is somewhat different, although you may have recognized that most JS engine exploits look the same once basic primitives are constructed.