On 25 Nov 2012, at 3:17 AM, "Will" <[email protected]> wrote:
> The idea would be that the webserver would handle that file and send it to > cgi and delete it. The web server would only handle the file when the upload of the file was complete. All the attacker needs to do is make sure lots of uploads start, upload 99% of their content, and then stop, never completing, and then repeat this pattern until you're out of disk. In theory your CGI program would have had the power to decide before allowing the upload to start whether it was willing to accept the file, perhaps because the user was a trusted user, or because enough space was available on disk, but by placing your proposed stream-to-file in the way the CGI is no longer able to do that. Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
