3 ms·
> This is because, in a change to historic competition rules, the system configuration was frozen last week, so the last-minute fix hasn't prevented exploitatio
by jedsmith 16y ago
> This is because, in a change to historic competition rules, the system configuration was frozen last week, so the last-minute fix hasn't prevented exploitation.
then later
> One possible reason for this is that Google published a Chrome update yesterday, closing at least 24 security flaws. The would-be Chrome attacker may have been depending on one of these flaws to attack the browser.
I thought the configuration was frozen last week. Was that only for Apple? On first read, this seems like a faulty conclusion based on the earlier statement.
- elliottcarlson 16y agoIt sounds like the system configuration being frozen doesn't change the browser updates that might occur last second.
- trotsky 16y agoYou're right about the inconsistency, it seems an older version of chrome would be the target. I think this rule was unannounced though, or maybe even made up in the last 24 hours as google and apple pushed updates. So understandable I think, or at least I made the same mistake :/
- blinkingled 16y agoAFAIK the contest requires you to exploit an previously unknown vulnerability. (Contest rules link is down on cansecwest site.) Which means even though Apple patched the 60 vulnerabilities the researcher used a one that was not known and thus not patched.