Web App Authentication: Find, Confirm & Fix (Basic)
Hands-on with Authentication Weakness (brute force) (CWE-307) in Acme Accounts's login feature. Safely reproduce it with an inert training tool (no working exploit), classify it, score it with CVSS, then apply the correct fix and verify.
Skills you will practice
- Secure web application concepts; Authentication Weakness (brute force) identification and prioritization; Web application testing; Rate limiting
- lockout and MFA
Certifications this lab maps to
This lab builds hands-on skills that appear on these certification exams. thinQtank Learning runs instructor-led training camps for each — click one to see upcoming classes.
The scenario
A penetration test flagged Acme Accounts's login feature as Authentication Weakness (brute force) (CWE-307). You are the app-security engineer. Start by understanding it.
What you will do
- Understand the feature and the finding4 steps
Open the engagement · Read the finding · Which weakness class? · Read the feature config
- Reproduce it safely5 steps
A normal login attempt · Flood the login · Capture the result · Review the evidence · …
- Assess the severity4 steps
Find the CVSS vector · Compute the base score · What is the base score? · Why this severity?
- Fix it4 steps
Which fix is right? · Baseline scan · Apply the fix · Confirm the config
- Verify3 steps
Verify with a scan · If it was already exploited? · Document the work
How this lab works
A real Linux-style console. Commands run against real files, so hashes, hex dumps and comparisons give real results.
A file browser where you can place evidence into the lab, either the file provided or one of your own.
Reset a single step, a whole task or the entire lab. The environment is rebuilt so you can try again cleanly.
Progress saves after every step. Close the tab and come back later; your files and answers are waiting.