Interactive scripts on the IIS 8.5 web server must be located in unique and designated folders.

From IIS 8.5 Site Security Technical Implementation Guide

Associated with: CCI-000381

SV-91581r2_rule Interactive scripts on the IIS 8.5 web server must be located in unique and designated folders.

Vulnerability discussion

CGI and ASP scripts represent one of the most common and exploitable means of compromising a web server. All CGI and ASP program files must be segregated into their own unique folder to simplify the protection of these files. ASP scripts must be placed into a unique folder only containing other ASP scripts. JAVA and other technology-specific scripts must also be placed into their own unique folders. The placement of CGI, ASP, or equivalent scripts to special folders gives the Web Manager or the SA control over what goes into those folders and to facilitate access control at the folder level.

Check content

Determine whether scripts are used on the web server for the target website. Common file extensions include, but are not limited to: .cgi, .pl, .vb, .class, .c, .php, .asp, and .aspx. All interactive programs must be placed in unique designated folders based on CGI or ASP script type. Open the IIS 8.5 Manager. Right-click the IIS 8.5 web site name and select Explore. Search for the listed script extensions. Each script type must be in its unique designated folder. If scripts are not segregated from web content and in their own unique folders, then this is a finding.

Fix text

All interactive programs must be placed in unique designated folders based on CGI or ASP script type. Open the IIS 8.5 Manager. Right-click the IIS 8.5 web server name and select Explore. Search for the listed script extensions. Move each script type to its unique designated folder. Set the permissions to the scripts folders as follows: Administrators: FULL TrustedInstaller: FULL SYSTEM: FULL ApplicationPoolId:READ Custom Service Account: READ Users: READ ALL APPLICATION PACKAGES: READ

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.