Authorization Code in Browser History

When a browser navigates to 'client.example/redirection_endpoint?code=abcd' as a result of a redirect from a provider's authorization endpoint, the URL including the authorization code may end up in the browser's history. An attacker with access to the device could obtain the code and try to replay it.

OAuth 2.0 Security Best Current Practice (SecBCP, section 4.3.1)


This threat is considered fully mitigated if all the test cases from one of the following test sets succeed.

Back to the threat overview