Security pattern / case archive

Trusted Header Authentication Bypass

A backend trusts a client-reachable identity header that should only be set by an authenticated gateway or reverse proxy.

Common discovery signals
  • The normal request is denied because no gateway identity is present.
  • Source or configuration names the trusted identity header and accepted principal.
  • Adding only that header changes the same request from denied to authorized.
Safe validation approach

Keep the method, route, and request state fixed, add one source-derived identity header, and stop after the protected read-only response is confirmed.

Related classifications

Related entries

Archive connections

Connected case files

01 record
CASE-023WEBVERSE
Connected evidence

CrocThis

Exposed Git Repository / Trusted Header Authentication Bypass

A public .git directory exposed the PHP authorization path. The same /admin/ request changed from 403 to 200 after adding the source-derived X-User identity, and both Caido and curl reached the protected operations console.