J-Security Center

Title: Microsoft IIS And PWS 8.3 Directory Name Vulnerability

Severity: HIGH

Description:

32bit Windows operating systems support long filenames, but also offer a means of compatibility with the older 8.3 filenames required by previous versions of DOS and Windows. This leads to problems with programs that have their own internal file security mechanisms. In Microsoft's IIS and PWS, requesting the 8.3 version of a file or directory effectively bypasses the security attributes that are referenced to the full, long version of the filename, with permissions being based instead on those of the parent directory.

Successful exploitation of this vulnerability could lead not only to unauthorized directory listings, disclosure of arbitrary files, but also to the remote execution of 'protected' scripts.

For example: with directory listing enabled for C:\inetpub\wwwroot\ and listing disabled for c:\inetpub\wwwroot\longsubdir\, a GET request for http://server/longsubdir/ will result in a permission denied error, as it should. However, a GET request for http://server/longsu~1/ will result in a successful directory listing.

Affected Products:

  • Cisco Building Broadband Service Manager 5.0.0
  • Cisco Call Manager 1.0.0
  • Cisco Call Manager 2.0.0
  • Cisco Call Manager 3.0.0
  • Cisco ICS 7750 0.0.0
  • Cisco IP/VC 3540 Video Rate Matching Module 0.0.0
  • Cisco Unity Server 2.0.0
  • Cisco Unity Server 2.2.0
  • Cisco Unity Server 2.3.0
  • Cisco Unity Server 2.4.0
  • Cisco uOne 1.0.0
  • Cisco uOne 2.0.0
  • Cisco uOne 3.0.0
  • Cisco uOne 4.0.0
  • Microsoft BackOffice 4.0.0
  • Microsoft BackOffice 4.5.0
  • Microsoft IIS 4.0.0
  • Microsoft NT Option Pack for NT 4.0 0.0.0
  • Microsoft Personal Web Server 4.0.0
  • Microsoft Windows 98
  • Microsoft Windows NT 4.0 Option Pack

Juniper Networks provides this content via a wide variety of sources and production methods. If notified of errors or omissions in the content of this page, Juniper Networks, at its discretion, will modify or remove the page or leave the content as is, depending on various factors including but not limited to the reputation and authority of the party providing the notification. Please use the contact information displayed elsewhere on this page to report any errors or omissions regarding the content on this page.