Bypassing Authentication Schema

Check List

Methodology

Black Box

Auth Type Manipulation

1

Log in to the target site, go to the authentication page, and check if it uses multiple types of authentication, such as password, email, Google, and Facebook

2

Enter the request using an incorrect password and email address. Intercept the POST request using Bupr Suite

3

Then examine the intercepted request and see if you see a parameter called auth_type

4

If you see such a parameter that specifies the type of authentication with Google or Facebook or password and email, send the request to the repeater

5

And then change the authentication type in the auth_type parameter to facebook

"auth_type": "email""facebook"
6

If the user information is displayed in the server response, the authentication bypass is confirmed


Email Domain Validation Bypass

1

Access registration form

2

Enter email test@redacted.com, Capture POST request in Burp

3

Notice server prepends or validates only suffix (@redacted.com)

email=bishal@redacted.com
4

Modify email domain to any external domain

email=bishal0x01@bugcrowdninja.com
5

Send request

6

Receive verification email at bishal0x01@bugcrowdninja.com

7

Click link, Account activated


Change The Letter Case

1

Use the enumerate Application command to perform the identification process and obtain the sensitive paths of the admin panel

2

Access known admin path

GET /admin HTTP/1.1
3

If it gives you a 403 error with a 401 in response, then send the following request

GET /AdMiN HTTP/1.1
GET /ADMIN HTTP/1.1
GET /aDmIn HTTP/1.1
GET /Admin HTTP/1.1
GET /aDMIN HTTP/1.1
4

If any variation returns 200 OK, Case sensitivity bypass confirmed


HTTP Method Bypass Auth

1

Make a request to the admin panel and check if it gives you a 403 in response

2

If it gives you a 403 error with a 401 then change the HTTP method to PUT or Patch or ...


Path Confusion Auth Bypass

1

Request a sensitive route like the panel or admin route and if it gives you a 403, try to mislead the route using the payload below

2

If the server response shows login or admin information, the vulnerability is confirmed


1

Navigate to the SignUp page of the target website, typically located at a URL like /signup or /register Open https://example.com/signup in the browser

2

Identify the “Full Name” input field in the SignUp form, which is prone to processing user input directly into database queries Find the text box labeled “Full Name” in the form

3

Enter the payload ' OR 1=1 -- into the Full Name field to attempt bypassing the query’s conditions and access unauthorized data Input John' OR 1=1 -- in the Full Name field

4

Click the “Sign Up” button to send the payload to the server via a POST request

5

Look for a generic error (“Invalid input”) or a 400/500 status code, indicating the payload was blocked, or unexpected success, suggesting a vulnerability

6

If a 400/500 error appears, modify the payload to ' OR 1=2 -- and submit again. Compare responses: if ' OR 1=1 -- allows form submission or data access (account creation without valid input) while ' OR 1=2 -- fails, it confirms SQL injection, as the true condition (1=1) altered the query’s logic


White Box

Cheat Sheet

Parameter Modification

Create Script

Run Script

Session ID Prediction

SQL Injection (HTML Form Authentication)

Create Script

Run Script

PHP Loose Comparison

Create Script

Run Script

Last updated