OWASP / OWASP/www-project-api-security-testing-framework
DVGA row 19: brute-force check not wired into GraphQL test case
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 19.
testBruteForceLockout (added in #97) lives in BrokenAuthenticationTestCase and is REST-oriented/path-pattern-gated. DVGA's "Weak Password (Brute Force)" vulnerability is on a GraphQL argument (systemDiagnostics), never reached. Needs a GraphQL-shaped equivalent.
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 docs/TRACEABILITY.md row 19 and inspect testBruteForceLockout in BrokenAuthenticationTestCase, including the REST-oriented path-pattern gating. Then examine how the GraphQL systemDiagnostics argument is exercised in the test cases. Done means a GraphQL-shaped brute-force lockout check covers the DVGA vulnerability and the relevant GraphQL test case reaches it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, java
- Domain
- api, security, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100