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

2FA broken logic

Link: https://portswigger.net/web-security/authentication/multi-factor/lab-2fa-broken-logic

PreviousUsername enumeration via subtly different responsesNextUsername enumeration via response timing

Last updated 3 months ago

Description:

This lab's two-factor authentication is vulnerable due to its flawed logic. To solve the lab, access Carlos's account page.

  • Your credentials: wiener:peter

  • Victim's username: carlos

You also have access to the email server to receive your 2FA verification code.

Proof of concept:

  1. Cek fitur autentikasi

  2. Analisa request dan response pada fitur tersebut. Dari hasil analisa didapati terdapat 2 Endpoint login, yang pertama adalah untuk memasukan username & password dan endpoint ke 2 untuk memasukan MFA-Code. Dari hasil analisa juga didapati, pada saat berhasil memasukan username & password yang valid akan mendapati session dan verify yang berisi username yang akan login nantinya

  3. Login kembali menggunakan akun testing (wiener:peter). Intercept request tersebut menggunakan burp suite intercept. Lakukan “Do Intercept” pada response dari request tersebut

  4. Ubah nilai pada parameter cookie verify dari username attacker menjadi username victim. Jika sudah, kirim kembali request tersebut

  5. Maka akan masuk kedalam halaman 2FA, dimana pada halaman ini harus menginputkan code MFA yang dikirimkan ke email korban. Namun, karena tidak dapat mengakses email korban, lakukan brute force untuk mendapatkan MFA code yang valid menggunakan burp suite intruder. Code yang valid ditandai dengan elngth response yang berbeda dengan request lain dan juga ditandai dengan menggunakan HTTP status code 302

  6. Jika sudah menemukan nilai code yang valid, coba inputkan code tersebut dan berhasil mengakses akun korban

Thanks, Stay Ethical & Happy Hacking! 🍻