Twitter | Search | |
Hacker Fantastic
Blackhats will be weaponizing spectre to steal session cookies from additional websites opened in the browser, especially financial sites. Enable site isolation in Chrome now.
Reply Retweet Like More
DEY! Jan 3
Replying to @hackerfantastic
Reply Retweet Like
π™ΉπšŽπš— πš‚πšŠπšŸπšŠπšπšŽ Jan 3
Replying to @hackerfantastic
Maybe also disable the Shared Array Buffer? chrome://flags/-array-buffer
Reply Retweet Like
What. Jan 3
Replying to @hackerfantastic
I have been using the feature in Chrome for the past few weeks since release and have noticed zero issues since enabling
Reply Retweet Like
Andy Gocke Jan 3
This link doesn't mention separated address space -- is there a more detailed description of how the feature works?
Reply Retweet Like
Justin List Jan 4
What about safari ? Does this apply to iOS too ?
Reply Retweet Like
Steven Tu πŸ”₯ AfrikaBurn + Sanctuary Jan 4
Replying to @hackerfantastic
Does clicking this link actually do this β€œsite isolation thing” or did all my data just get jacked? Because it just opened a new browser window and no messages. Looks dodgey as hell.
Reply Retweet Like
Silviu Jan 4
Do mozilla's multi account containers mitigate this for Firefox?
Reply Retweet Like
mallory, alice & bob Jan 4
Replying to @Tuism @hackerfantastic
I always right-click stuff on twitter (even tho I think T does new tabs for me) and I just get a google chrome help page. Doesn't "do" anything for you tho.
Reply Retweet Like
mallory, alice & bob Jan 4
Fan went up immediately, but I may have to turn it off for this reason: "DevTools: Chrome Developer Tools don't fully support cross-site iframes with site isolation." Unfortunately my work does *all* its content via iframes.
Reply Retweet Like
Steven Tu πŸ”₯ AfrikaBurn + Sanctuary Jan 4
Weird, clicking the link from tweetdeck gave me nothing, had to copy paste the link to get to support. Thanks for the headsup.
Reply Retweet Like
Erroneus Jan 4
Reply Retweet Like
Alberto Bengoa πŸ˜ƒ Jan 4
Al loro con esto, que el bug de los procesadores va a traer cola.
Reply Retweet Like
Pablo Cirre Jan 4
suena bien, donde puedo encontrar mas info?
Reply Retweet Like
Akshet Jan 4
Replying to @hackerfantastic
AFAICT site isolation doesn't fix this problem because the attacker can always include an image tag with src to a target site and that will cause a GET and add the cookie to the renderer memory which they can then get their hands on. See:
Reply Retweet Like
Hacker Fantastic Jan 4
Replying to @Akshet
It won't because it will be in its own process for the target site rendering, Google are recommending the same step, post PoC if you can violate it.
Reply Retweet Like
Akshet Jan 4
Replying to @hackerfantastic
Only if the cookie has SameSite as mentioned in the link... BoA, Chase, GitHub, Google... practically no one sets that flag
Reply Retweet Like
Akshet Jan 4
Replying to @hackerfantastic
This can be weaponized so quick into draining my bank accounts, getting control over my google and stealing all of my private repo that I am surprised that this part of the problem was more aggressively discussed
Reply Retweet Like
Akshet Jan 4
Replying to @hackerfantastic
s/was more/wasn't more/
Reply Retweet Like
Vinny Troia Jan 4
How would you steal a session cookie from a site without having some sort of execution ability on the server to begin with?
Reply Retweet Like