1000 Ways to Die in Mobile Oauth
summary
Field study of 600 popular mobile apps finds 149 using OAuth and 59.7% vulnerable; bugs include embedded client secrets, redirect‑URI hijacks, missing consent pages, omitted state tokens, and token‑swap/login‑CSRF attacks. Live demos show Instagram’s old flaw and Wish still vulnerable, an attacker capturing or swapping access tokens to fully impersonate victims, plus web‑view cookie exfiltration that yields long‑term Facebook session takeover. Recommendations: verify redirect URLs, keep secrets off clients, use server checks and OpenID Connect.
AI-written summary · about
chapters (9)
- 0:00Start
- 13:46Brief history of OAuth
- 17:52Vulnerability - Locally stored secrets
- 26:49Authorization VS Authentication
- 28:11Vulnerability. Using authorization flow for authentication
- 32:39OAuth2 Code Authorization Flow
- 33:22Code Authorization Flow. Verify authorization code
- 36:36Vulnerability - Lack of Consent
- 39:52OAuth Security State Token
related talks
27mSecurity Issues In OAuth/OIDC Implementations
18mHow to Hack OAuth
47mTop X OAuth 2 Hacks
36mHow To Hack OAuth|
23mUniversal Cross-app Attacks: Exploiting and Securing OAuth 2.0 in...
46mFixing authentication and authorization
53mGetting API Security Right
01h 05mCommon mistakes and misconceptions in Web App Security using OAuth 2.0 and OpenId Connect
