session - OAuth 2.0 malicious interceptor on browser -


i going through auth 2.0 protocol [1], along proof key rfc [2]. explains how protocol protects against malicious apps listening network traffic. however, i'm unable understand how auth 2.0 protocol protects against malicious code working on browser itself.

let's take simple case of proof key rfc protocol. generate high-entropy code verifier, have store somewhere in browser (possibly in cookies/browser's local storage) use again token. now, in case there malicious code executing on browser, can access cookies/local storage , code verifier.

is there protocol enhancement (similar rfc-7636) protects against cookie based exploits? if not, how mitigate it?

[1] https://tools.ietf.org/html/rfc6749

[2] https://tools.ietf.org/html/rfc7636

oauth 2.0 caters different types of clients i.e. web clients, in-browser clients , native mobile app clients.

the pcke oauth 2.0 mechanism designed native mobile apps. allows public clients protect against malicious apps , attackers may hold of authorization code.

when dealing web clients, pcke mechanism not needed since these attacks can prevented use of confidential client client secret stored server-side.

when dealing in-browser clients there's problem mention in general hope lost when malicious code running in browser.

in summary: pkce not mechanism defend against cross site scripting attacks in browsers.


Comments

Popular posts from this blog

Command prompt result in label. Python 2.7 -

javascript - How do I use URL parameters to change link href on page? -

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -