Buffer overflow in the browser kernel in Google Chrome before
220.127.116.11 allows remote HTTP servers to cause a denial of service
(application crash) or possibly execute arbitrary code via a crafted
This is hardmasked, so we do not have to hurry.
chromium-bin-9999 is hardmasked, but -0_p* are not (just ~x86 keyworded), so let's fix that one ;)
From http://code.google.com/p/chromium/issues/detail?id=14508, chromium trunk was fixed in revision 18687, so for us it's <=www-client/chromium-bin-0_p18366 vulnerable. I've just removed this version from portage
I've tested the "listener of death" from the bugreport with 0_p19106 (current ebuild in portage), and it did not crash
Thanks! Closing noglsa.