Authentication
bb-huge π€ , Personal bug bounty findings hub and bug bounty orchestration for multiple agents
npx -y skills add ShulkwiSEC/bb-huge --skill authenticationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Complete PortSwigger deep-dive with exact payloads for every lab variant including zero-day techniques
SKILL.md
5.6 KB, as published. Nobody here has run it
Authentication β Complete Deep Dive
Deep-Dive Lab Playbook β Every PortSwigger lab variant with exact payloads, bypass techniques, and zero-day extensions. π’ Apprentice π‘ Practitioner π΄ Expert
When to Use
- BSCP certification prep
- Real-world bug bounty hunting
- Building exploitation chains
- Understanding bypass techniques
Prerequisites
- Burp Suite Professional
- Burp Collaborator / interactsh
- Browser with proxy configured
Workflow
Phase 1: Reconnaissance
- Identify input vectors, parameters, and application behavior.
Phase 2: Exploitation
- Apply standard lab payloads.
Phase 3: Zero-Day Escalation
- Fuzz filters, bypass WAFs, and chain with other vulns.
Lab Playbooks
Lab 1: Username enum different responses π’ APPRENTICE
Burp Intruder with username wordlist. Check response length/content difference: Invalid username vs Incorrect password.
Lab 2: 2FA simple bypass π’ APPRENTICE
After login, skip /login2 (2FA page) and navigate directly to /my-account.
Lab 3: Password reset broken logic π’ APPRENTICE
POST /forgot-password?temp-forgot-password-token=TOKEN HTTP/1.1
temp-forgot-password-token=TOKEN&username=carlos&new-password-1=hacked&new-password-2=hacked
Change username to victim. Token validation doesn't check user ownership.
Lab 4: Subtly different responses π‘ PRACTITIONER
Check for trailing period: Invalid username or password vs Invalid username or password.
Lab 5: Response timing π‘ PRACTITIONER
Long password β longer response time for valid usernames (bcrypt hash computed). Use X-Forwarded-For: 1.1.1.Β§1Β§ to bypass IP lock.
Lab 6: Broken brute-force IP block π‘ PRACTITIONER
Login with valid creds every 2 attempts to reset the IP counter. Alternate: validβattackβvalidβattack.
Lab 7: Username enum via account lock π‘ PRACTITIONER
Locked account = account exists. Send 5 attempts for each username. Locked response = valid user.
Lab 8: 2FA broken logic π‘ PRACTITIONER
POST /login2 HTTP/1.1
Cookie: verify=carlos
mfa-code=Β§1234Β§
Change verify cookie to victim, brute force 4-digit MFA code.
Lab 9: Stay-logged-in cookie crack π‘ PRACTITIONER
Cookie = Base64(username:MD5(password)). Decode, crack MD5 hash.
Lab 10: Offline password cracking π‘ PRACTITIONER
Steal cookie via XSS β decode Base64 β crack MD5 hash offline with hashcat.
Lab 11: Password reset poisoning middleware π‘ PRACTITIONER
POST /forgot-password HTTP/1.1
X-Forwarded-Host: EXPLOIT-SERVER
username=carlos
Reset link sent to carlos uses your host β steal reset token.
Lab 12: Brute-force via password change π‘ PRACTITIONER
Password change function reveals different errors for wrong vs correct current password. Brute force current password via this oracle.
Lab 13: Multiple credentials per request π΄ EXPERT
{"username":"carlos","password":["123456","password","qwerty",...]}
Send password array β server tries all in one request, bypassing rate limiting.
Lab 14: 2FA brute force π΄ EXPERT
Macro in Burp: auto-login β auto-get 2FA page β brute force code β repeat. Set session handling rule to use macro.
Blue Team Detection
- Monitor access logs for anomalous payloads.
- Implement strict input validation and parameterized queries where applicable.
- Create WAF rules masking generic attack patterns.
Zero-Day Research
When standard technique fails:
- Identify the filter/WAF
- Fuzz with Burp Intruder custom wordlists
- Search GitHub/Twitter for new bypasses
- Chain with other vulns for escalation
- Try encoding variants: URL, double-URL, unicode, hex
Key Concepts
| Concept | Description |
|---|---|
| PortSwigger Vectors | Standardized approaches to vulnerability classes. |
| Payload Encoding | Modifying payloads to bypass basic string matching WAFs. |
Output Format
Vulnerability Deep-Dive Report
==============================
Target Vector: [Endpoint]
Bypass Technique: [Explanation of bypass]
Payload Used: [Payload]
Impact Explanation: [Impact]
π΅ Blue Team
- Deploy robust WAF rules to detect anomalies.
- Monitor logs for unusual access patterns.
π‘οΈ Remediation & Mitigation Strategy
- Input Validation: Sanitize and strictly type-check all inputs.
- Least Privilege: Constrain component execution bounds.
π Shared Resources
For cross-cutting methodology applicable to all vulnerability classes, see:
_shared/references/elite-chaining-strategy.mdβ Exploit chaining methodology and high-payout chain patterns_shared/references/elite-report-writing.mdβ HackerOne-optimized report writing, CWE quick reference_shared/references/real-world-bounties.mdβ Verified disclosed bounties by vulnerability class