Portswigger
  • Portswigger
  • Server-Side Request Forgery
    • Server-Side Request Forgery (SSRF)
  • SSRF with filter bypass via open redirection vulnerability
  • Blind SSRF with out-of-band detection
  • Cross-Site Scripting
    • Cross-Site Scripting (XSS)
  • Reflected XSS into a JS string with angle brackets and double&single quotes HTML-encoded escape
  • XSS into a template literal w/ angle brackets, single, double quotes, backslash & backticks Escaped
  • Authentication
    • Authentication
  • Username enumeration via subtly different responses
  • 2FA broken logic
  • Username enumeration via response timing
  • Username enumeration via account lock
  • Password reset poisoning via middleware
  • Path Traversal
    • Path Traversal
  • File path traversal, traversal sequences stripped with superfluous URL-decode
  • File path traversal, traversal sequences blocked with absolute path bypass
  • Business Logic Vulnerabilities
    • Business Logic Vulnerabilities
  • Insufficient workflow validation
  • Inconsistent handling of exceptional input
  • Server-Side Template Injection
    • Server-Side Template Injection
  • Basic server-side template injection
  • Basic server-side template injection (code context)
  • SQL Injection
    • SQL Injection
    • Blind SQL injection with conditional responses
  • SQL injection UNION attack, retrieving data from other tables
  • SQL injection attack, listing the database contents on non-Oracle databases
  • API Testing
    • API Testing
  • Exploiting an API endpoint using documentation
  • Exploiting a mass assignment vulnerability
  • Finding and exploiting an unused API endpoint
  • JWT ATTACK
    • JWT Attack
    • JWT authentication bypass via unverified signature
  • JWT authentication bypass via jku header injection
  • JWT authentication bypass via flawed signature verification
  • HTTP HOST HEADER ATTACKS
    • HTTP Host header attacks
  • Basic password reset poisoning
  • Host header authentication bypass
  • No SQL Injection
    • NoSQL Injection
  • Detecting NoSQL injection
  • Exploiting NoSQL operator injection to bypass authentication
  • Exploiting NoSQL injection to extract data
  • FILE UPLOAD VULNERABILITIES
    • File Upload Vulnerabilities
  • Web shell upload via obfuscated file extension
  • OAuth Authentication
    • OAuth Authentication
  • OAuth account hijacking via redirect_uri
  • ACCESS CONTROL VULNERABILITIES
    • Access Control Vulnerabilities
  • User ID controlled by request parameter with data leakage in redirect
  • User ID controlled by request parameter with password disclosure
  • User role controlled by request parameter
  • User role can be modified in user profile
  • URL-based access control can be circumvented
  • INFORMATION DISCLOSURE VULNERABILITIES
    • Information Disclosure Vulnerabilities
  • Information disclosure in version control history
  • XML external entity injection
    • XML External Entity (XXE) Injection
  • Exploiting XXE using external entities to retrieve files
  • Exploiting blind XXE to retrieve data via error messages
  • Blind XXE with out-of-band interaction
  • Blind XXE with out-of-band interaction via XML parameter entities
  • OS COMMAND INJECTION
    • OS Command Injection
  • Blind OS command injection with out-of-band data exfiltration
  • PROTOTYPE POLLUTION
    • Prototype Pollution
  • Privilege escalation via server-side prototype pollution
  • WEB CACHE POISONING
    • Web Cache Poisoning
  • Web cache poisoning via an unkeyed query parameter
Powered by GitBook
On this page

Username enumeration via subtly different responses

Link: https://portswigger.net/web-security/authentication/password-based/lab-username-enumeration-via-subtly-different-responses

PreviousAuthenticationNext2FA broken logic

Last updated 3 months ago

Description: This lab is subtly vulnerable to username enumeration and password brute-force attacks. It has an account with a predictable username and password, which can be found in the following wordlists:

To solve the lab, enumerate a valid username, brute-force this user's password, then access their account page.

Proof of concept:

  1. Akses halaman login target

  2. Lakukan request login dengan credentials acak, analisa request dan response menggunakan burp suite. Terlihat jika, credentials salah akan muncul response “Invalid username or password.”

  3. Kirim request tersebut ke burp suite intruder. Atur attack type menjadi “clusterbomb” dan atur taget payload pada value parameter username dan password. Tambahkan payload username dan password menggunakan payload yang telah disediakan. Selanjutnya, tambahkan pengaturah grep match “Invalid username or password.” untuk memfilter payload mana saja yang mengandung kata tersebut dan tidak sehingga akan memudahkan menemukan payload yang benar

  4. Terlihat, pada hasil brute force terdapat beberapa payload yang tidak memiliki response “Invalid username or password.” namun, ketika dilihat payload-payload tersebut mengandung response yang sama namun terdapat perbedaan sedikit yaitu response yang diberikan adalah “Invalid username or password” (tanpa titik pada akhir kalimat). Dapat dispekulasikan bahwa username tersebut valid namun password dari username tersebut masih salah. Lihat status code yang berbeda, dan didapati payload yang memilik status code “302” (Dialihkan/Berhasil Login)

  5. Coba login menggunakan akun tersebut, dan berhasil mengakses halaman dashboard akun tersebut.

Thanks, Stay Ethical & Happy Hacking! 🍻

Candidate usernames
Candidate passwords