Windows NT based Web Servers File Access Vulnerability
Privacy and Legal Notice
INFORMATION BULLETIN
I-025A: Windows NT based Web Servers File Access Vulnerability
January 30, 1998 21:00 GMT
PROBLEM: Some Windows NT based web servers allow access to 8.3 format
filenames. This can allow unauthorized access to files via
their 8.3 compatible name.
PLATFORM: Microsoft Internet Information Server and Peer Web Server 4.0,
Netscape FastTrack 2.x
DAMAGE: By exploiting this vulnerability, remote users may gain
unauthorized access to files accessed by the web server.
SOLUTION: Apply the fixes listed in Section 3 of this advisory.
VULNERABILITY Exploit information involving this vulnerability has been made
ASSESSMENT: publicly available.
Introduction
============
Windows NT file systems support filenames of up to 255 characters. For
compatibility purposes, a short filename (the 8.3 filename) is usually
created for each file, and can be used by older applications to access
directories and files with long names. Web server file protection of
directories and files in long filename (not 8.3) formats can often allow
access to the short name (8.3) equivalent without restriction. Some
Windows NT based Web servers base their access control check for permissions
using the long filename only, and do not include the short name that may
be used as an alias. For example, if there was a file named
noteightdotthree.htm, and it was protected at the file level by the web
server (NOT the NTFS file system itself), the access of the short name
noteig~1.htm is possible. This also applies to directories. Note that NTFS
level file restrictions are always applied correctly because they are not
inherently tied to the long name, but to the name stored on disk, which the
long name references. Some web servers allow you to set access permissions
in places other than NTFS, however it is the implementation of these controls
that are causing the vulnerability.
The characteristics of this vulnerability also appear in IIS 3.0 and PWS
3.0, but only at the directory level. Using the long file name IIS or PWS
3.0 to protect an execute only directory inside a read-execute or read-only
is not recommended. Microsoft has stated that they do not consider it a
bug, but a 'bad' practice.
This vulnerability may easily affect other Windows NT based WWW servers.
CIAC recommends that you check with your vendor to ensure your WWW server
does not exhibit this characteristic.
Problem
=======
This vulnerability permits attackers to gain unauthorized access to files
on the Web server. It may be used to download the source code of
server scripts in some configurations. If exploited it can give an
intruder access to any file that the web server can access.
Prevention
==========
Microsoft IIS 4.0 and PWS 4.0
==============================
Microsoft has developed a hot-fix to correct the problem. CIAC has
verified that the hot-fix corrects the problem described above, but has
not done any regression testing. Instructions for installing it are
available from Microsoft. Microsoft recommends that you update your
Emergency Repair Disk before you apply the patch, as they have not
regression tested the hot-fix.
Microsoft's patch location:
Windows NT 4.0 (CIAC recommends that Service Pack 3 is installed first):
ftp://ftp.microsoft.com/bussys/IIS/iis-public/fixes/usa/security/sfn-fix/
Microsoft IIS 3.0 and PWS 3.0
==============================
Although Microsoft does not consider this a bug, CIAC recommends that you
ensure directory access controls are not nested. Verify that WWW server
protections are not being used to enforce protection for execute-only
directories that reside in read-only or read-execute directories.
Netscape FastTrack 2.x
=======================
Netscape will be producing patches.
_______________________________________________________________________
Thanks to:
NtBugtraq Mailing List (NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM)
David LeBlanc <dleblanc@iss.net>
Michael Howard <mikehow@microsoft.com>
_______________________________________________________________________
CIAC services are available to DOE, DOE Contractors, and the NIH. CIAC
can be contacted at:
Voice: +1 925-422-8193 (7 x 24)
FAX: +1 925-423-8002
STU-III: +1 925-423-2604
E-mail: ciac@ciac.org
World Wide Web: http://www.ciac.org/
Anonymous FTP: ftp.ciac.org
This document was prepared as an account of work sponsored by an
agency of the United States Government. Neither the United States
Government nor the University of California nor any of their
employees, makes any warranty, express or implied, or assumes any
legal liability or responsibility for the accuracy, completeness, or
usefulness of any information, apparatus, product, or process
disclosed, or represents that its use would not infringe privately
owned rights. Reference herein to any specific commercial products,
process, or service by trade name, trademark, manufacturer, or
otherwise, does not necessarily constitute or imply its endorsement,
recommendation or favoring by the United States Government or the
University of California. The views and opinions of authors expressed
herein do not necessarily state or reflect those of the United States
Government or the University of California, and shall not be used for
advertising or product endorsement purposes.
UCRL-MI-119788
[Privacy and Legal Notice]