Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly render sublists #43

Closed
philippederyck opened this issue Mar 24, 2024 · 2 comments
Closed

Properly render sublists #43

philippederyck opened this issue Mar 24, 2024 · 2 comments

Comments

@philippederyck
Copy link
Contributor

Section 5.1.2 contains a sublist, but it is not rendered properly

### Persistent Token Theft {#payload-persistent-theft}

This attack scenario is a more advanced variation on the Single-Execution Token Theft scenario ({{payload-single-theft}}). Instead of immediately stealing tokens upon the execution of the malicious payload, the attacker sets up the necessary handlers to steal the application's tokens on a continuous basis. This scenario consists of the following steps:

- Execute malicious JS code
- Setup a continuous token theft mechanism (e.g., on a 10-second time interval)
	  - Obtain tokens from the application's preferred storage mechanism (See {{token-storage}})
	  - Send the tokens to a server controlled by the attacker
	  - Store the tokens
- Wait until the opportune moment to abuse the latest version of the stolen tokens

The crucial difference in this scenario is that the attacker always has access to the latest tokens used by the application. This slight variation in the payload already suffices to counter typical defenses against token theft, such as short lifetimes or refresh token rotation.

For access tokens, the attacker now obtains the latest acce
philippederyck added a commit to philippederyck/OAUTHWG-oauth-browser-based-apps that referenced this issue Apr 11, 2024
@philippederyck
Copy link
Contributor Author

philippederyck commented Apr 11, 2024

@aaronpk I don't know where to find an updated draft from #45, so I cannot check if this now renders correctly. It should though ...

philippederyck added a commit to philippederyck/OAUTHWG-oauth-browser-based-apps that referenced this issue Apr 11, 2024
@aaronpk
Copy link
Member

aaronpk commented May 1, 2024

Yep looks good now
image

@aaronpk aaronpk closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants