Authorization code and access token leakage through redirect vulnerabilities

OAuth implementations risk leaking authorization codes via HTTP Referrer headers and access tokens through URL hash fragments. Redirect hijacking vulnerabilities enable account takeover, and optional CSRF state token protection is frequently ignored in implementations.

Sources

• https://biggo.com/news/202508251913_OAuth_Implementation_Challenges
• https://www.securing.pl/pl/what-is-going-on-with-oauth-2-0-and-why-you-should-not-use-it-for-authentication/
• https://www.securing.pl/en/what-is-going-on-with-oauth-2-0-and-why-you-should-not-use-it-for-authentication/
• https://howik.com/oauth-2-0-common-issues
• https://www.descope.com/blog/post/oauth-2-0-vs-oauth-2-1
• https://duendesoftware.com/learn/7-common-security-pitfalls-oauth-2-0-implementations
• https://www.apisec.ai/blog/oauth-2-0-common-security-flaws
• https://www.vaadata.com/blog/understanding-oauth-2-0-and-its-common-vulnerabilities/
• https://www.ietf.org/archive/id/draft-ietf-oauth-security-topics-25.html

Collection History