News for hackers. Stuff that matters.
Re:Hacker News CSRF Vulnerability by etjossem on Thursday February 25, 2016 @03:59PM (#11177743)
The implications depend on your app. If the user doesn't notice being logged into a new account, they may go on to create data in the attacker's account that they expect to be private (e.g. YouTube watch history).

On e-commerce sites, they might add a credit card - thereby allowing the attacker to use it.

Fortunately, HN doesn't have these risks, but it's a good illustration of how CSRF works in the real world.

Re:Hacker News CSRF Vulnerability by ghayes on Thursday February 25, 2016 @04:11PM (#11177828)
Plus if you made the account name "new" or "top posts" or something, it could take weeks for me to notice that it didn't say my username at the top right.
Re:Hacker News CSRF Vulnerability by lucb1e on Thursday February 25, 2016 @04:05PM (#11177793)
Good points indeed. I never thought of adding anti-CSRF measures to login forms, only while logged in, so I'll start doing that :)
Re:Hacker News CSRF Vulnerability by r1ch on Thursday February 25, 2016 @04:24PM (#11177915)
Another good reason for login CSRF tokens is to prevent a malicious page from submitting lots of invalid logins and getting an account / IP locked or rate limited.