OAuth Security Cheatsheet

http://www.oauthsecurity.com/

by homakov • 12 years ago

125 15 12 years ago

oauthsecurity.com

homakov4• 12 years ago

It's using free plan on heroku, so if it will be down repo is available at https://github.com/homakov/oauthsecurity

aaronpk• 12 years ago

@homakov I'd be happy to host this content on the oauth.net website if you'd like.

homakov4• 12 years ago

I think just an external link will be great, because I don't want to remove the sakurity logo :)

lukasm• 12 years ago

Why didn't you use github page or S3. It's static page isn't it?

homakov4• 12 years ago

Yes but i serve it with sinatra

thepumpkin1979• 12 years ago

off-topic: I see you made a commit two hours ago but when I try to click on the commiter the link is not enabled, try this guide to set your name and github username so all your commits are linked to your github user account: https://help.github.com/articles/setting-your-username-in-gi...

pm24601• 12 years ago

Thanks for this list. I will be reviewing our site at whalepath.com to make sure we are not vulnerable.

btw, linkedin has implemented a number of the counter measures listed in:

* static redirects

* checking that the redirect listed is the same for all calls.

* fast expiration of code.

stormbrew• 12 years ago

The place I work for deals with about 20 different site's oauth processes and it's amazing how widely varied they are. Some of them let you restrict the redirect_uri while others don't, some of them still need you to send a login/password pair for the first request rather than do an oauth flow, but then still use oauth-style tokens all over the place. A couple of them require that the token be passed as a query string parameter instead of as a header for all requests. Being responsibly secure with all of them is quite difficult. It doesn't help that it's very difficult to have a development environment work properly with them, so doing active work against them is often painful.

OAuth is basically a complete mess, implementation-wise, and that's really sad since it's such a promising and useful premise.

MAGZine• 12 years ago

That's really unfortunate. I read through the RFC, and IIRC it is pretty consistent on those details. Can't stop people from badly implementing a spec :(

fnom2• 12 years ago

i've heard great stuff about oauth.io . they try to provide an abstractionlayer that handles the various different implementations (often buggy or not to spec) of oauth.

indeyets2• 12 years ago

that might be true, but I don't like idea of having a MiTM. That's an additional point of potential security issues

lstamour• 12 years ago

Some good points. Other links of interest: http://tools.ietf.org/html/rfc6819 and OWASP cheat sheets, including ones on authentication in general: https://www.owasp.org/index.php/OWASP_Cheat_Sheet_Series amongst other resources on Google ;-)

indeyets2• 12 years ago

You missed the obvious: using OAuth2 without TLS =)

And paranoid part of my brain suggests that using OAuth1.0a is still preferred even if over TLS

homakov4• 12 years ago

This is another kind of threat but yes, MITM is game over for oauth2

OAuth Security Cheatsheet

Related Stories