Skip to content

WSTG-ATHN-03: Add credential stuffing and distributed brute force testing guidance#1356

Open
YK-03 wants to merge 1 commit intoOWASP:masterfrom
YK-03:wstg-athn03-clean
Open

WSTG-ATHN-03: Add credential stuffing and distributed brute force testing guidance#1356
YK-03 wants to merge 1 commit intoOWASP:masterfrom
YK-03:wstg-athn03-clean

Conversation

@YK-03
Copy link
Copy Markdown
Contributor

@YK-03 YK-03 commented Mar 9, 2026

This PR expands the How to Test section of WSTG-ATHN-03 (Testing for Weak Lock Out Mechanism) by adding guidance for testing credential stuffing and distributed brute force attacks.

Modern authentication attacks often rely on credential stuffing using leaked credentials and distributed infrastructure such as botnets or rotating proxy networks. Applications that rely solely on IP-based lockout mechanisms may be vulnerable to these attacks.

What this PR adds

  • Guidance on testing credential stuffing scenarios
  • Methodology for detecting distributed brute force attempts
  • Example authentication request
  • Tooling examples (Burp Suite Intruder, Hydra, ffuf)
  • Recommendations for evaluating lockout protections against distributed attacks

Why this change is useful

Credential stuffing is one of the most common authentication attack vectors today. Expanding this section helps testers evaluate whether lockout mechanisms are resilient against modern attack patterns rather than only traditional single-source brute force attempts.

@github-actions

This comment has been minimized.

@YK-03 YK-03 force-pushed the wstg-athn03-clean branch from f4e8411 to 92df62d Compare March 9, 2026 16:28
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 9, 2026

📝 Markdown Linting Issues

Total Errors: 2

document/4-Web_Application_Security_Testing/04-Authentication_Testing/03-Testing_for_Weak_Lock_Out_Mechanism.md

Errors: 2

  • Line 43 - MD040/fenced-code-language: Fenced code blocks should have a language specified [Context: "triple-backtick"]
  • Line 62 - MD040/fenced-code-language: Fenced code blocks should have a language specified [Context: "triple-backtick"]

Please fix these issues before merging. See .markdownlint.json for project style rules.

@kingthorin
Copy link
Copy Markdown
Collaborator

Please be aware that I won't be super active this week or next. If you aren't getting reviews it isn't for lack of appreciation, I'm just busy with some family stuff.

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

Successfully merging this pull request may close these issues.

2 participants