Solution Available for File Viewers Vulnerability (231368)
The information in this article applies to:
- Microsoft Site Server 3.0
- Microsoft Site Server 3.0 Commerce Edition
- Microsoft Commercial Internet System 2.0
- Microsoft BackOffice Server 4.0
- Microsoft BackOffice Server 4.5
- Microsoft Internet Information Server 4.0
This article was previously published under Q231368 SYMPTOMS
Microsoft has identified a vulnerability that occurs in some file viewers that are included with Microsoft Site Server and Internet Information Server.
The vulnerability could allow a Web site visitor to view, but not to change, files on the server, provided that the visitor knows or guesses the name of each file and has access rights to the file based on the Windows NT Access Control Lists (ACLs).
CAUSE
The file viewer tools do not restrict which files a user can view.
RESOLUTIONSite Server 3.0To resolve this problem, obtain the latest service pack for Site Server 3.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
219292 How to Obtain the Latest Site Server 3.0 Service Pack
This problem was first corrected in Site Server 3.0 Service Pack 3. IIS 4.0
A fix has been developed for IIS 4.0, and has been posted to the following Internet location as Fix2450I.exe (Intel) or Fix2450A.exe (Alpha):
Please see the following article in the Microsoft Knowledge Base for more information about this fix:
232449 Sample ASP Code May be Used to View Unsecured Server Files
WORKAROUND
To eliminate the vulnerability on your Web server that can be caused by these file viewers, you should:
- Remove the affected file viewers, unless they are specifically required on the
Web site. The following file viewers are
affected: ViewCode.asp, ShowCode.asp, Code.asp, CodeBrws.asp, and Winmsdp.exe.
Depending on the specific installation, not all of these files may
be present on a server. There may be multiple copies of
some files, so you should perform a full search of your servers
to locate all copies.
- In accordance with standard security guidelines, file permissions
should always be set to enable Web visitors to gain access to only the files
they need, and no others. Files that are needed by Web
visitors should provide the least privilege needed. For example,
files that Web visitors need to be able to read but not write should
be set to read-only.
- As a general rule, sample files and virtual roots (vroots) should always be deleted
from a Web server before you put it into production. If sample files and vroots are needed, file access permissions should be used to regulate access to
them as appropriate
Modification Type: | Minor | Last Reviewed: | 9/22/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbpending kbprb kbQFE KB231368 |
---|
|