OWASP / OWASP/www-project-api-security-testing-framework
DVGA row 22: JWT-forge argument-based auth bypass field-name heuristic too narrow
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 150
- Forks
- 41
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 3
Description
Tracked in docs/TRACEABILITY.md, DVGA row 22.
testArgumentBasedAuthBypass (#102) targets CURRENT_USER_FIELD_NAMES (me/viewer/currentUser/profile) with a forged token argument. Ran against DVGA's me(token) field but found no match — DVGA's actual mechanism may differ from the field-name heuristic used. Investigate the real field/argument shape and broaden detection accordingly.
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 testArgumentBasedAuthBypass (#102) and its CURRENT_USER_FIELD_NAMES heuristic, then compare it with the DVGA me(token) field and the argument shape described in the issue. Check docs/TRACEABILITY.md row 22 for the tracked expectation. Done means the test detects DVGA's actual forged-token argument pattern without losing coverage for the existing field names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100