Forum Moderators: phranque
On an affected server, it would have returned a directory listing to the attacking program, which would then exploit the bug to spread the worm further.
However, people will constantly throw exploits against any web server, so keep an eye on security updates.
Jon.
The 302 response code might be of concern. I seem to recall that, depending on how the server is configured, this might be okay. (Try copying the entire URL from your log file and making the request against your server.)
Since there are both encoded characters and ".." references in the path, I am guessing that the server is not locked down as well as it could be. If you run the IIS lockdown tool and/or install the URL Scan utility from MS, you won't get these in your log file. (they are blocked before they make it through to IIS) Both of those tools are available from the MSDN (msdn.microsoft.com) website.