3 ms·
I noticed that browsers and curl were doing something with .. on the client side. Try telnet to the port and typing the GET by hand.
by tyingq 7y ago
I noticed that browsers and curl were doing something with .. on the client side. Try telnet to the port and typing the GET by hand.
- Thorrez 7y agoYou're partially right that curl is blocking '..'. But it's not blocking '%2e%2e'. I got it to avoid blocking '..' with the --path-as-is flag. I redid the tests, with curl's --path-as-is flag, as well as with raw TCP (via netcat), and SimpleHTTPServer is still not vulnerable.