News for hackers. Stuff that matters.
Re:A Modest Proposal for Improving Website Authentication by kijin on Tuesday May 21, 2013 @10:54AM (#5744028)
CSRF attacks should be relatively harmless if directed at the login page. They would have zero effect unless they got the credentials right, and an attacker who has access to your login credentials has no need for CSRF attacks, they can just log right in.

Edit: I'm wrong. See below.

Re:A Modest Proposal for Improving Website Authentication by mixedbit on Tuesday May 21, 2013 @10:56AM (#5744044)
Login CSRF attacks are known to be harmful: https://en.wikipedia.org/wiki/Cross-site_request_forgery#For...

The attacker doesn't brute force someone's credentials, but uses own credentials to log the victim as the attacker.

Re:A Modest Proposal for Improving Website Authentication by kijin on Tuesday May 21, 2013 @11:18AM (#5744229)
Ah, didn't realize that. Thanks for pointing it out. I suppose the header should contain some sort of nonce, then.

To keep things as simple as possible, I propose:

    Auth-Spec: type=plain; action=/login; method=POST; fields=email,password,nonce:8977340152
The "colon syntax" could also be used where the name of a required field is different from the defaults (another problem that I overlooked). For example, WordPress uses "log" for the username and "pwd" for the password, so it would be "fields=log:username,pwd:password".

It wouldn't be possible to require a nonce, though, because it would break backward compatibility with sites that are already vulnerable anyway. As an option for new or updated websites, though, it would be a good idea to add a nonce field.