Great blog post and exploit, thanks for sharing (and highlighting the patch gapping issue once again). Bug was originally found by Fuzzilli btw... =)
Patch-gapping in practice: Google Chrome edition (by @_2can of our nDay team)https://blog.exodusintel.com/2019/09/09/patch-gapping-chrome/ …
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Can you point out some ideas on shipping updates? The project is so widely used (also by 3rd parties, like Qutebrowser, Electron, etc), so having such gaps sounds like something to be expected. Have you approached distributors and exchanged about it?
-
With my
#qutebrowser maintainer hat on: The main issue is that Chrome changes insanely fast and Google doesn't care about third-parties using Chromium. IIRC, QtWebEngine devs need about two man-months to update the underlying Chromium (with millions of changed lines of code). - Još 2 druga odgovora
Novi razgovor -
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.