XSL ISAPI Contains Non-Secure Code that Results in Access to IIS Files (324322)



The information in this article applies to:

  • Microsoft Internet Information Server 4.0
  • Microsoft Internet Information Services 5.0
  • Microsoft XML 2.5
  • Microsoft XML 2.6
  • Microsoft XML 3.0

This article was previously published under Q324322
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

SYMPTOMS

When certain error conditions are met, IIS files may be exposed to clients who browse the Web site if you are using the XSL ISAPI filter.

RESOLUTION

To resolve this problem, you must download and install a new filter.
  1. Determine which version of the XSL ISAPI filter you are currently using, and then download the new filter from one of the following locations:Note that it is extremely important to note which version is being used in IIS. If you are not sure, review the documentation that is located on the download page of the filter. The extensible nature of the filter makes it possible to apply the wrong update to your version type.

  2. Click Start, click Programs, click Windows NT 4.0 Option Pack, click Internet Information Server, and then click Internet Services Manager.
  3. When the ISM opens, right-click the server name, and then click Properties to open the Master Properties dialog box.
  4. In the Master Properties dialog box, make sure that WWW is listed in the drop-down list, and then click Edit.
  5. On the ISAPI Filters tab, make sure that the XSL ISAPI filter is listed. The filter is installed and updated by the installer.
  6. Stop and restart the service to activate the changes.
NOTE: Although no known compatibility issues exist between earlier versions, Microsoft recommends that you install and fully test the new XSL ISAPI version in a non-production environment before you use it in a production environment.

STATUS

Microsoft has confirmed that this is a problem in IIS versions 4.0 and 5.0 and MSXML versions 2.5, 2.6, 3.0.

Modification Type:MinorLast Reviewed:6/23/2005
Keywords:kbbug kbpending KB324322