Cyber Risks · PortSwigger Research

Lab: Routing-based SSRF

Summary: PortSwigger's lab demonstrates routing-based SSRF through the Host header, where replacing the Host value with an address in the 192.168.0.0/24 range lets an attacker reach an insecure intranet admin panel on an internal IP. Solving it requires sending a request to /admin/delete with a copied CSRF token and a username parameter set to carlos, using Burp Collaborator's default public server because the platform's firewall blocks interactions with arbitrary external systems.

What you should know: The Host header is attacker-controlled input that many internal networks still trust for routing, so a single request can reach an admin panel that was never meant to be internet-facing - and delete a user without any credentials.

Read the original at PortSwigger Research ↗

Topics
Vulnerabilities & Patching
Related