|
|
|
|
|
by jchw
344 days ago
|
|
> Like, if the administrator put something inside that directory Path traversal bugs allowing written files to land in the cgi-bin used to be a huge exploit vector. Interestingly, some software actually relied on being able to write executable files into the document root, so the simple answer of making the permissions more limited is actually not a silver bullet. If you've never seen or heard of this, ¯\_(ツ)_/¯ > Unix doesn't have folders Great and very important point. Someone should go fix all of these bugs: https://github.com/search?q=repo%3Atorvalds%2Flinux%20folder... |
|
Of course, disabling ExecCGI in one directory won't help if you do have path traversal holes in your upload-handling code. I'm not convinced that disabling CGI will help if attackers can use a path traversal hole to upload malicious executables to arbitrary paths you can write to. They can overwrite your .bashrc or your FastCGI backend program or whatever you're likely to execute. CGI seems like the wrong thing to blame for that.
Why are you linking me to a "Sign in to search code on GitHub" page?