Microsoft has reported four new remote vulnerabilities in IIS. The first vulnerability is a cross site scripting issue in the error page returned to advise of a redirected URL. This could allow for the theft of cookie based credentials and other attacks. IIS 4.0, 5.0, and 5.1 are affected. The second issue is a buffer overflow related to server side includes. If a malformed server side include page was uploaded to an IIS server then requested, a buffer would be overrun allowing arbitrary code execution with user level permissions. IIS 5.0 is affected. The third and fourth issues are denial of service vulnerabilities. ASP pages containing excessively large headers could cause IIS to fail when the page is requested by a remote user. IIS 4.0 and 5.0 are affected. IIS does not properly handle WebDAV requests over 49,153 bytes to the 'PROPFIND' and 'SEARCH' request methods. As a result, if a long WebDAV request is received, IIS will fail. IIS 5.0 and 5.1 are affected. In the case of...
Microsoft has reported four new remote vulnerabilities in IIS. The first vulnerability is a cross site scripting issue in the error page returned to advise of a redirected URL. This could allow for the theft of cookie based credentials and other attacks. IIS 4.0, 5.0, and 5.1 are affected. The second issue is a buffer overflow related to server side includes. If a malformed server side include page was uploaded to an IIS server then requested, a buffer would be overrun allowing arbitrary code execution with user level permissions. IIS 5.0 is affected. The third and fourth issues are denial of service vulnerabilities. ASP pages containing excessively large headers could cause IIS to fail when the page is requested by a remote user. IIS 4.0 and 5.0 are affected. IIS does not properly handle WebDAV requests over 49,153 bytes to the 'PROPFIND' and 'SEARCH' request methods. As a result, if a long WebDAV request is received, IIS will fail. IIS 5.0 and 5.1 are affected. In the case of both denial of service issues, IIS 5.0 and 5.1 will automatically restart. IIS 4.0 must be manually restarted if it fails.
