How can session-persistence of a web application account lead to re-infection of the browser and OS [closed]
I recently read a blog post that mentioned there is a way to highjack a user's account by stealing their session cookies, and then persisting the logged in state by extending the expiration of the cookie indefinitely. This would also mean bypassing any 2FA. This was in particular about Gmail accounts but I supposed it could happen to any web application relying on cookies in a similar nature.
This is kind of like session-fixation, but the article implied that even if the user logged out the attacker could still gain access to the session, which frankly, i don't understand how that's possible.
But let's assume that the session is highjacked, I'd like to know how exactly that leads to browser/OS compromise.
Say that a Gmail account is compromised in this manner. I would think that there is a known browser exploit that is triggered by running malicious JavaScript. I guess an attacker would have to embed the JavaScript in the users inbox somehow, such that when the user logs in again their browser is exploited. Am I right in this understanding? What are some other possible ways this could happen?
If this is in fact true, what are some preventative/detection measures one could take here? I know you can run the browser in a VM. Would using something like SELinux here help? Because I suppose that once the browser is infected, it is installing an executable on the OS somewhere. Is it possible to constrain the browser's execution using a tool like SElinux effectively?
