Top X OAuth 2 Hacks
summary
Concrete OAuth 2 implementation bugs are analyzed: reused authorization codes enabling replay/token theft, open redirect plus improper redirect-URI validation allowing attacker-registered clients to capture auth codes, and putting access tokens in URLs (leaking via logs/Referer). The talk cites real incidents affecting Facebook, Google, Microsoft, GitLab, PayPal and Dropbox and shows exploits using whitelist quirks, URI spoofing and DNS/localhost tricks; recommended fixes are exact redirect-URI matching and never placing tokens in URLs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:07Why OAuth 2 was created
- 8:31OAuth 2 flaws and IETF decisions
- 17:27OAuth 2 is not auth
- 22:07Reusing authorization code
- 24:12Open redirect and attacks
- 29:17Native app errors and client flow
- 32:07Access token in URL risks
- 34:17CSRF and related attacks
- 37:12OAuth 2 as auth misuse
- 39:40Advanced redirect URI attacks
- 44:03Secure OAuth 2 tips
- 45:08Q&A
related talks
36mHow To Hack OAuth|
47mHacking OAuth
18mHow to Hack OAuth
23mUniversal Cross-app Attacks: Exploiting and Securing OAuth 2.0 in...
37mHacking OAuth Pitfalls and Remedies
01h 02mOpenID Connect & OAuth 2.0 – Security Best Practices
47m1000 Ways to Die in Mobile Oauth
01h 00mBreaking and securing OAuth 2.0 in frontends at NDC Security
