id: xff-403-bypass info: name: X-Forwarded-For 403-forbidden bypass author: vavkamil severity: info description: Template to detect 403 forbidden endpoint bypass behind Nginx/Apache proxy & load balancers, based on X-Forwarded-For header. metadata: max-request: 3 tags: fuzz,fuzzing http: - raw: - | GET / HTTP/1.1 Host: {{Hostname}} Accept: */* - | GET / HTTP/1.1 Host: {{Hostname}} Accept: */* X-Forwarded-For: 127.0.0.1, 0.0.0.0, 192.168.0.1, 10.0.0.1, 172.16.0.1 - | GET /test.txt HTTP/1.1 Host: {{Hostname}} Accept: */* X-Forwarded-For: 127.0.0.1, 0.0.0.0, 192.168.0.1, 10.0.0.1, 172.16.0.1 matchers: - type: dsl dsl: - "status_code_1 == 403 && status_code_2 != 403" - "status_code_1 == 403 && status_code_3 != 403" condition: or # digest: 4b0a00483046022100d604fd662fc1f70df85d821c77dc004a6057b4dec83c0987665f26944f7c22ff022100b65077257980c7f5e27827fd59c1dfdede384dfe49cae028c8acd25e187e3e29:922c64590222798bb761d5b6d8e72950