HTTP 403/401 Bypass Auditor
A skill for systematically testing HTTP access control bypasses on web applications.
When to Use This Skill
Use this skill when:
- You encounter 403 Forbidden or 401 Unauthorized responses
- You need to test if access controls can be bypassed
- You're performing web application security assessments
- You want to enumerate protected resources
- You're testing authentication/authorization mechanisms
Testing Methodology
Follow this systematic approach to test for bypass vulnerabilities:
1. HTTP Method Fuzzing
Try different HTTP verbs to access the protected resource:
Methods to test:
GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH
- Custom/invented methods:
INVENTED, HACK
What to check:
- Response codes (200, 403, 401, 404, 500)
- Response headers (Content-Length, Server, X-Powered-By)
- Response body differences
- HEAD requests returning 200 with Content-Length may indicate accessible content
Method override headers:
X-HTTP-Method-Override: PUT
X-HTTP-Method-Override: DELETE
TRACE method:
- Can reveal headers added by intermediate proxies
- May expose internal infrastructure details
2. HTTP Header Fuzzing
Host header manipulation:
- Change Host to arbitrary values
- Try
Host: localhost
- Remove Host header entirely
User-Agent variations:
- Test different User-Agent strings
- Use common bypass User-Agents
- Try empty User-Agent
Proxy/Forwarding headers (try with 127.0.0.1):
X-Originating-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-Forwarded: 127.0.0.1
Forwarded-For: 127.0.0.1
X-Remote-IP: 127.0.0.1
X-Remote-Addr: 127.0.0.1
X-ProxyUser-Ip: 127.0.0.1
X-Original-URL: 127.0.0.1
Client-IP: 127.0.0.1
True-Client-IP: 127.0.0.1
Cluster-Client-IP: 127.0.0.1
Path bypass headers:
X-Original-URL: /admin/console
X-Rewrite-URL: /admin/console
Special headers to fuzz:
- Content-Type variations
- Accept headers
- Authorization headers
- Custom application headers
3. Path Fuzzing
URL encoding bypasses:
/%2e/path (dot encoding)
/%252e/path (double URL encoding)
/%ef%bc%8fpath (Unicode full-width slash)
Path manipulation techniques:
- Case variations:
/SECRET vs /secret
- Trailing slashes:
/secret/
- Dot sequences:
/secret/., /./secret/..
- Double slashes:
//secret//
- Semicolon injection:
/;/secret, /.;/secret, //;//secret
- File extensions:
/secret.json (Ruby apps)
API version bypasses:
/v3/users_data/1234 → /v1/users_data/1234
- Try different API version numbers
Parameter pollution:
- JSON:
{"user_id":"<legit_id>","user_id":"<victims_id>"}
- Query:
user_id=ATTACKER_ID&user_id=VICTIM_ID
- Array injection:
{"id":[111]} instead of {"id":111}
- Nested objects:
{"id":{"id":111}}
4. Parameter Manipulation
Value changes:
- Increment/decrement IDs:
id=123 → id=124
- Boundary testing:
-234, 0, 99999999
- Special characters in values
Parameter additions:
- Add admin flags:
?id=124&isAdmin=true
- Add authentication parameters
- Add debug parameters
Parameter removal:
- Remove required parameters
- Remove authentication tokens
Parameter reordering:
- Change parameter order in query string
- May bypass validation logic
5. Protocol Testing
HTTP version changes:
- HTTP/1.1 → HTTP/1.0
- HTTP/1.1 → HTTP/2.0
- Different protocol versions may have different handling
Protocol switching:
- HTTP → HTTPS
- HTTPS → HTTP
- May bypass SSL/TLS checks
6. Infrastructure Bypasses
Direct IP access:
- Get IP or CNAME of domain
- Contact directly without DNS
- May bypass domain-based restrictions
Archive testing:
Server stress:
- Send rapid common GET requests
- May cause race conditions or timeout bypasses
7. Authentication Bypass
Common credentials to test:
admin admin
admin password
admin 1234
admin admin1234
admin 123456
root toor
test test
guest guest
Authentication methods:
- Basic authentication
- Digest authentication
- NTLM authentication
- Session token manipulation
Automated Testing
Use these tools for systematic testing:
Advanced Techniques
HTTP Request Smuggling:
- If behind a proxy, test for request smuggling vulnerabilities
- Can bypass proxy-based access controls
Hop-by-Hop Headers:
- Abuse hop-by-hop headers to bypass proxy restrictions
- Headers like
Connection, Keep-Alive, Proxy-Authenticate
Unicode Fuzzing:
- Use Unicode character lists for path fuzzing
- Test at different positions:
/FUZZsecret, /FUZZ/secret, /secretFUZZ
Reporting Findings
When documenting bypass vulnerabilities:
- Endpoint: The protected URL
- Original Response: 403/401 status and body
- Bypass Method: Which technique worked
- Modified Request: The successful request details
- Impact: What was accessed or what could be accessed
- Remediation: How to fix the vulnerability
Safety and Ethics
- Only test systems you have authorization to test
- Document all findings for remediation
- Avoid destructive operations (DELETE, PUT with data modification)
- Respect rate limits to avoid DoS
- Follow responsible disclosure practices
Quick Reference
Most effective bypasses to try first:
- HTTP method changes (HEAD, OPTIONS, TRACE)
- Path case variations and trailing slashes
- X-Forwarded-For header with 127.0.0.1
- URL encoding variations
- Parameter pollution
- API version changes
- Direct IP access
Response indicators of success:
- Status code changes from 403/401 to 200
- Content-Length changes
- Different response body
- New headers appear
- Server error (500) may indicate partial bypass
1---2name: http-bypass-auditor3description: How to audit and test for HTTP 403/401 bypass vulnerabilities. Use this skill whenever the user mentions access control testing, forbidden page bypasses, authentication bypass, 403 errors, 401 errors, HTTP method fuzzing, header manipulation, path traversal testing, or any web security testing involving restricted resources. Make sure to use this skill when users want to test if they can access protected endpoints through various bypass techniques, even if they don't explicitly mention 'bypass' or '403'.4metadata:5 source: https://skillmd.com/skills/abelrguezr/http-bypass-auditor6---78# HTTP 403/401 Bypass Auditor910A skill for systematically testing HTTP access control bypasses on web applications.1112## When to Use This Skill1314Use this skill when:15- You encounter 403 Forbidden or 401 Unauthorized responses16- You need to test if access controls can be bypassed17- You're performing web application security assessments18- You want to enumerate protected resources19- You're testing authentication/authorization mechanisms2021## Testing Methodology2223Follow this systematic approach to test for bypass vulnerabilities:2425### 1. HTTP Method Fuzzing2627Try different HTTP verbs to access the protected resource:2829**Methods to test:**30- `GET`, `HEAD`, `POST`, `PUT`, `DELETE`, `CONNECT`, `OPTIONS`, `TRACE`, `PATCH`31- Custom/invented methods: `INVENTED`, `HACK`3233**What to check:**34- Response codes (200, 403, 401, 404, 500)35- Response headers (Content-Length, Server, X-Powered-By)36- Response body differences37- HEAD requests returning 200 with Content-Length may indicate accessible content3839**Method override headers:**40- `X-HTTP-Method-Override: PUT`41- `X-HTTP-Method-Override: DELETE`4243**TRACE method:**44- Can reveal headers added by intermediate proxies45- May expose internal infrastructure details4647### 2. HTTP Header Fuzzing4849**Host header manipulation:**50- Change Host to arbitrary values51- Try `Host: localhost`52- Remove Host header entirely5354**User-Agent variations:**55- Test different User-Agent strings56- Use common bypass User-Agents57- Try empty User-Agent5859**Proxy/Forwarding headers (try with 127.0.0.1):**60- `X-Originating-IP: 127.0.0.1`61- `X-Forwarded-For: 127.0.0.1`62- `X-Forwarded: 127.0.0.1`63- `Forwarded-For: 127.0.0.1`64- `X-Remote-IP: 127.0.0.1`65- `X-Remote-Addr: 127.0.0.1`66- `X-ProxyUser-Ip: 127.0.0.1`67- `X-Original-URL: 127.0.0.1`68- `Client-IP: 127.0.0.1`69- `True-Client-IP: 127.0.0.1`70- `Cluster-Client-IP: 127.0.0.1`7172**Path bypass headers:**73- `X-Original-URL: /admin/console`74- `X-Rewrite-URL: /admin/console`7576**Special headers to fuzz:**77- Content-Type variations78- Accept headers79- Authorization headers80- Custom application headers8182### 3. Path Fuzzing8384**URL encoding bypasses:**85- `/%2e/path` (dot encoding)86- `/%252e/path` (double URL encoding)87- `/%ef%bc%8fpath` (Unicode full-width slash)8889**Path manipulation techniques:**90- Case variations: `/SECRET` vs `/secret`91- Trailing slashes: `/secret/`92- Dot sequences: `/secret/.`, `/./secret/..`93- Double slashes: `//secret//`94- Semicolon injection: `/;/secret`, `/.;/secret`, `//;//secret`95- File extensions: `/secret.json` (Ruby apps)9697**API version bypasses:**98- `/v3/users_data/1234` → `/v1/users_data/1234`99- Try different API version numbers100101**Parameter pollution:**102- JSON: `{"user_id":"<legit_id>","user_id":"<victims_id>"}`103- Query: `user_id=ATTACKER_ID&user_id=VICTIM_ID`104- Array injection: `{"id":[111]}` instead of `{"id":111}`105- Nested objects: `{"id":{"id":111}}`106107### 4. Parameter Manipulation108109**Value changes:**110- Increment/decrement IDs: `id=123` → `id=124`111- Boundary testing: `-234`, `0`, `99999999`112- Special characters in values113114**Parameter additions:**115- Add admin flags: `?id=124&isAdmin=true`116- Add authentication parameters117- Add debug parameters118119**Parameter removal:**120- Remove required parameters121- Remove authentication tokens122123**Parameter reordering:**124- Change parameter order in query string125- May bypass validation logic126127### 5. Protocol Testing128129**HTTP version changes:**130- HTTP/1.1 → HTTP/1.0131- HTTP/1.1 → HTTP/2.0132- Different protocol versions may have different handling133134**Protocol switching:**135- HTTP → HTTPS136- HTTPS → HTTP137- May bypass SSL/TLS checks138139### 6. Infrastructure Bypasses140141**Direct IP access:**142- Get IP or CNAME of domain143- Contact directly without DNS144- May bypass domain-based restrictions145146**Archive testing:**147- Check https://archive.org/web/148- See if resources were previously accessible149- May reveal historical access patterns150151**Server stress:**152- Send rapid common GET requests153- May cause race conditions or timeout bypasses154155### 7. Authentication Bypass156157**Common credentials to test:**158```159admin admin160admin password161admin 1234162admin admin1234163admin 123456164root toor165test test166guest guest167```168169**Authentication methods:**170- Basic authentication171- Digest authentication172- NTLM authentication173- Session token manipulation174175## Automated Testing176177Use these tools for systematic testing:178179| Tool | Purpose |180|------|---------|181| [byp4xx](https://github.com/lobuhi/byp4xx) | 4xx error bypass automation |182| [bypass-403](https://github.com/iamj0ker/bypass-403) | 403 bypass testing |183| [forbiddenpass](https://github.com/gotr00t0day/forbiddenpass) | Forbidden page bypass |184| [403 Bypasser](https://portswigger.net/bappstore/444407b96d9c4de0adb7aed89e826122) | Burp extension |185| [Forbidden Buster](https://github.com/Sn1r/Forbidden-Buster) | Automated bypass testing |186| [NoMoreForbidden](https://github.com/akinerk/NoMoreForbidden) | 403 bypass tool |187188## Advanced Techniques189190**HTTP Request Smuggling:**191- If behind a proxy, test for request smuggling vulnerabilities192- Can bypass proxy-based access controls193194**Hop-by-Hop Headers:**195- Abuse hop-by-hop headers to bypass proxy restrictions196- Headers like `Connection`, `Keep-Alive`, `Proxy-Authenticate`197198**Unicode Fuzzing:**199- Use Unicode character lists for path fuzzing200- Test at different positions: `/FUZZsecret`, `/FUZZ/secret`, `/secretFUZZ`201202## Reporting Findings203204When documenting bypass vulnerabilities:2052061. **Endpoint**: The protected URL2072. **Original Response**: 403/401 status and body2083. **Bypass Method**: Which technique worked2094. **Modified Request**: The successful request details2105. **Impact**: What was accessed or what could be accessed2116. **Remediation**: How to fix the vulnerability212213## Safety and Ethics214215- Only test systems you have authorization to test216- Document all findings for remediation217- Avoid destructive operations (DELETE, PUT with data modification)218- Respect rate limits to avoid DoS219- Follow responsible disclosure practices220221## Quick Reference222223**Most effective bypasses to try first:**2241. HTTP method changes (HEAD, OPTIONS, TRACE)2252. Path case variations and trailing slashes2263. X-Forwarded-For header with 127.0.0.12274. URL encoding variations2285. Parameter pollution2296. API version changes2307. Direct IP access231232**Response indicators of success:**233- Status code changes from 403/401 to 200234- Content-Length changes235- Different response body236- New headers appear237- Server error (500) may indicate partial bypass