This one’s no joke. If you don’t have auto updates on for Chrome, stop what you are doing and update right this second... immediately after that, email your CEO and explain how insane it is that you had to do anything manual to protect your org when it WAS automatic by default.https://twitter.com/USCERT_gov/status/1123394019160199168 …
-
-
Replying to @kidmystic @SwiftOnSecurity
Uhh… can you give us any additional info? Under active exploitation? Trivial enough to be exploitable within hours of patch release? Capable of allowing sandbox escape? (Google & CERT aren't saying anything particularly interesting.)
1 reply 0 retweets 0 likes -
Replying to @arekfurt @SwiftOnSecurity
I’m reading between the lines with the ‘we released a patch so quickly that the High CVE hasn’t even been written yet’ to imply some urgency.
2 replies 0 retweets 11 likes
I wouldn't read between the lines so much. US-CERT (not to be confused with CERT) does a Current Activity update for every Chrome update. It's not immediately obvious why, as IMO, if that's actionable information you're doing Chrome wrong.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.