SpyderTracks
We love you Ukraine
It's not even that difficult from a security perspective, hash to the browser that's hashed to the specific systems UEFI block.If the session cookie only worked on the browser it was created for, and was hashed as such, it would never have been able to be used to login anywhere else anyway. With all of this stuff I would go to the root cause. The root cause is that the session cookie was duplicated.
From here there are a chain of events, any break in the chain would potentially stop the event from happening. I think that shows that there are many shortcomings still in internet/browser security. I'm not surprised by any of that and I was aware of just about every step in the chain. The one thing that I didn't realise is that any cookie can be opened from any system anywhere as long as you are using the same browser (you can likely even use a different browser). I thought session cookies were more secure, but I guess they just store the session code/identification unhashed..... rather than being secure.
If the session cookie was hashed and linked to the browser that created it to generate the hash, this would never have happened.
If the server recognised or took action from a session being created in one location and then accessed from a different location, this would never have happened.
If the platform requested confirmation of credentials for notable requests/actions, this would never have happened.
All 3 areas should be patched. My point is that I wasn't actually aware of the first. The latter 2 have always been about simplicity and ease of access, different for typical end users though compared to businesses. There should be additional checks for higher profile accounts regardless.
That would surely be as bulletproof as UEFI which let's face it is the best security we currently know on hardware?