search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Microsoft Internet Information Server (IIS) vulnerable to DoS when URL request exceeds maximum allowed length

Vulnerability Note VU#521059

Original Release Date: 2002-04-10 | Last Revised: 2002-04-10

Overview

Intruders may be able to cause the IIS service to fail by sending a particular kind of overly-long URL.

Description

ISAPI is a programming interface to IIS that can be used to modify or extend the behavior of IIS. Programs written using ISAPI are known as either filters or extension, depending on the way in which they're implemented. One of the primary differences is that extensions only run when called (by a reference in a URL) whereas filters run for every URL submitted to the server. For more information on the difference between filters an extensions, see http://msdn.microsoft.com/library/en-us/vccore/html/_core_What_Is_the_Difference_Between_an_ISAPI_Server_Extension_and_a_Filter.3f.asp.

There is an ISAPI filter that ships as part of Microsoft Fronpage Extensions and ASP.NET that handles overly long URLs by replacing them with a null value. When IIS attempts to process the page (to send it back to the client as an error message) an access violation results. Other ISAPI filters may engage in similar behavior, which would trigger the same vulnerability. However, the only known extension to trigger this error ships with ASP.NET and Front Page Extensions. Quoting from Microsoft Security Bulletin MS02-018,

The sole ISAPI filter known to generate the error that results in the access violation ships only as part of FrontPage Server Extensions and ASP.NET. ASP.NET is not installed by default, and FPSE can be uninstalled if desired. 

If you have custom extensions or filters, you may wish to examine them to see if they would trigger this behavior too.

Impact

An intruder could cause the IIS service to fail. IIS 5.0 and 5.1 will automatically restart, though a sustained attack could be mounted relatively easily; IIS 4.0 would have to be manually restarted.

Solution

Apply a patch as described in MS02-018.

Vendor Information

521059
 
Affected   Unknown   Unaffected

Microsoft

Updated:  April 10, 2002

Status

  Vulnerable

Vendor Statement

See http://www.microsoft.com/technet/security/bulletin/ms02-018.asp

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us email.


CVSS Metrics

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A

References

Acknowledgements

Our thanks to Microsoft Corporation, upon whose advisory this document is based.

This document was written by Shawn V. Hernan.

Other Information

CVE IDs: CVE-2002-0072
Severity Metric: 33.30
Date Public: 2002-04-10
Date First Published: 2002-04-10
Date Last Updated: 2002-04-10 19:13 UTC
Document Revision: 4

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.