search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Microsoft Internet Information Server (IIS) vulnerable to buffer overflow via inaccurate checking of delimiters in HTTP header fields

Vulnerability Note VU#454091

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

Overview

A buffer overflow in IIS could allow an intruder to execute arbitrary code the the privileges of the ASP ISAPI extension.

Description

Like all web servers, IIS parses HTTP headers and decomposes them into the constituent parts. As part of this processing, IIS checks for delimiters that are supposed to mark boundaries within the headers. By constructing a carefully chosen HTTP request, and intruder to cause IIS to incorrectly parse an HTTP header, and place the incorrect results into a buffer that is too small. For more information, see Microsoft Security Bulletin MS02-018.

Impact

An intruder can interrupt the ordinary operation of a vulnerable IIS server or execute arbitrary code with the privileges of ASP ISAPI extension, ASP.DLL. On IIS 4.0, ASP.DLL runs as part of the operating system thus allowing an intruder to take full administrative control. On IIS 5.0 and 5.1, ASP.DLL runs with the privileges of the IWAM_computername account.

Solution

Apply a patch as described in Microsoft Security Bulletin MS02-018.

Until a patch can be applied, you may wish to disable the ASP ISAPI extension by using the IIS Lockdown tool, available at http://www.microsoft.com/technet/security/tools/locktool.asp. Additionally, the URLScan tool can help reduce the impact of this vulnerability.

Vendor Information

No information available at this time.


CVSS Metrics

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

References

Credit

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-0150
Severity Metric: 51.30
Date Public: 2002-04-10
Date First Published: 2002-04-10
Date Last Updated: 2002-04-10 20:39 UTC
Document Revision: 5

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