Reduce maximum lifetime of OAuth authorization code (10.4.3)
Open
Beginner friendly
Nobody has claimed this yet.
V10 (prev V51)
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Current 10.4.3 reads:
10.4.3 Verify that the authorization code is short‑lived. The maximum lifetime can be up to 10 minutes for L1 and L2 applications and up to 1 minute for L3 applications.
Reading:
- this thread;
- the ConsentFix attack description;
- issue 230 on Oauth 2.1,
I think it would make sense to reduce this to 1 minutes / 30 seconds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with requirement 10.4.3 in the ASVS source and compare its current lifetime wording with the OAuth browser-swapping thread, the ConsentFix attack description, and OAuth 2.1 issue 230 linked here. Update the requirement to reflect the agreed maximums, then verify the rendered standard still states the intended values.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100