←back to thread

Escaping the Chrome Sandbox Through DevTools

(ading.dev)
406 points vk6 | 2 comments | 17 Oct 24 05:55 UTC | HN request time: 0.723s | source
Show context
Etheryte ◴[17 Oct 24 07:57 UTC] No.41867389[source]▶
Given the severity, I can't help but feel that this is underpaid at the scale Google is at. Chrome is so ubiquitous and vulnerabilities like these could hit hard. Last thing they need to do is to send the signal that it's better to sell these on the black market.
replies(9): >>41867499 #>>41867548 #>>41867653 #>>41867666 #>>41867873 #>>41868146 #>>41868628 #>>41868995 #>>41869073 #
1. grokkedit ◴[17 Oct 24 08:51 UTC] No.41867653[source]▶
they say: `This also means that, unfortunately, the bug will not work on stable builds of Google Chrome since the release channel is set to the proper value there`

So it's only working on Chromium, a way smaller attack surface than the whole Chrome users

replies(1): >>41869055 #
2. Thorrez ◴[17 Oct 24 12:34 UTC] No.41869055[source]▶
Slight correction: it worked on Chromium and on Google Chrome canary.