Report generated by XSS.CX at Tue Nov 16 10:52:06 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

1.1. http://www.dailyfinance.com/quotes/linear-technology-corporation/lltc/nas [REST URL parameter 3]

1.2. http://www.dailyfinance.com/quotes/linear-technology-corporation/lltc/nas [REST URL parameter 3]

2. Source code disclosure

3. Cross-domain POST

4. Cross-domain script include

5. Email addresses disclosed


1. Cross-site scripting (reflected)  next
There are 2 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://www.dailyfinance.com/quotes/linear-technology-corporation/lltc/nas [REST URL parameter 3]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a39f1%2522%253e%253cscript%253ealert%25281%2529%253c%252fscript%253ea5c664aa146 was submitted in the REST URL parameter 3. This input was echoed as a39f1"><script>alert(1)</script>a5c664aa146 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 block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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

Remediation detail

There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /quotes/linear-technology-corporation/lltca39f1%2522%253e%253cscript%253ealert%25281%2529%253c%252fscript%253ea5c664aa146/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:52 GMT
Server: Apache
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:52 GMT; Path=/
Content-Language: en
Content-Length: 60046
Keep-Alive: timeout=5, max=899
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Quote, News & Summar
...[SNIP]...
<input value="LLTCA39F1"><SCRIPT>ALERT(1)</SCRIPT>A5C664AA146" id="navsearch_field" name="sym" class="search" maxlength="25" alt="Enter a symbol here" type="text" />
...[SNIP]...
1.2. http://www.dailyfinance.com/quotes/linear-technology-corporation/lltc/nas [REST URL parameter 3]  previous

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 39f79'%3be55ca221ad was submitted in the REST URL parameter 3. This input was echoed as 39f79';e55ca221ad in the application's response.

This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

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

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 /quotes/linear-technology-corporation/lltc39f79'%3be55ca221ad/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:53 GMT
Server: Apache
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:53 GMT; Path=/
Content-Language: en
Content-Length: 59904
Keep-Alive: timeout=5, max=992
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Quote, News & Summar
...[SNIP]...
<!--
var relegenceTopics='LLTC39F79';E55CA221AD';
var RTN_SNIPPET_SIZE = '300';
var RTN_HOVER_TIMEOUT = '16000';
// -->
...[SNIP]...
2. Source code disclosure  previous  next

Summary

Severity:   Low
Confidence:   Tentative
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

Issue detail

The application appears to disclose some server-side source code written in ASP.

Issue background

Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.

Issue remediation

Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.

Request

GET /quotes/linear-technology-corporation/lltc/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:41 GMT
Server: Apache
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Content-Language: en
Content-Length: 176464
Keep-Alive: timeout=5, max=991
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>LLTC: LINEAR TECHNOL
...[SNIP]...
<!--
<%
String clientid=f.r("sl.client_id");
String channelid=f.r("sl.channel_id.quotes.quotesandnews");
String squery=Utils.sponsoredLinkSearchTerm(SYMBOL, channelid);
%>
-->
...[SNIP]...
3. Cross-domain POST  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

Issue detail

The page contains a form which POSTs data to the domain search.aol.com. The form contains the following fields:

Issue background

The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.

Request

GET /quotes/linear-technology-corporation/lltc/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:41 GMT
Server: Apache
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Content-Language: en
Content-Length: 176464
Keep-Alive: timeout=5, max=991
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>LLTC: LINEAR TECHNOL
...[SNIP]...
<ul id="GH_dualsearchbox" class="GH_hat_UL"><form action="http://search.aol.com/aol/search?q=" method="post" name="bb_topform" id="dualsearch" target="_blank">
                       <input type="text" onblur="javascript:if(this.value=='')this.value='Search the Web' ;removecolor();" value="Search the Web" onkeypress="return submitHeaderSearch(event);" onfocus="this.value='
...[SNIP]...
4. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

Issue detail

The response dynamically includes the following scripts from other domains:

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.

Request

GET /quotes/linear-technology-corporation/lltc/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:41 GMT
Server: Apache
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Content-Language: en
Content-Length: 176464
Keep-Alive: timeout=5, max=991
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>LLTC: LINEAR TECHNOL
...[SNIP]...
<link rel="canonical" href="/quotes/linear-technology-corporation/lltc/nas" />
<script language="javascript1.1" src="http://o.aolcdn.com/ads/adsWrapper.js" type="text/javascript"></script>
...[SNIP]...
<body class="module" id="quotetest.page" >


<script type="text/javascript" src="http://o.aolcdn.com/aim/web-aim/aimapi.js"></script>
<script type="text/javascript" src="http://cta.aol.com/script/cta.js"></script>

<script src="http://o.aolcdn.com/dailyfinance/tools/static_c/__1020103104/js/??webaim.js,relegenceapi.js,relegence.js,RelegenceAjax.js,RelegenceNews.js,RelegenceTab.js,bootstrap.js,supertabs.js,crossdomain.js,swfobject-2_2.js,MarketsUpdater.js,QuoteUpdater.js,HomeBlock.js,QuoteInfo.js,Headlines.js,HeatUpdater.js" type="text/javascript"></script>
...[SNIP]...
</style>
<script type="text/javascript" src="http://o.aolcdn.com/os/money/dailyfinance/js/gh/jquery-1.3.2.min.js"></script>
<script type="text/javascript" src="http://o.aolcdn.com/art/merge/?f=/df_js/jquery.globalheader-1.3.js&f=/df_js/jquery.globalsearchbox-1.3.js&f=/df_js/jslib1.2.js&f=/df_js/df-search0.6.js&f=/df_js/smartbox1.7.4.js&expsec=2600000"></script>
...[SNIP]...
</script>

            <script language="JavaScript" src="http://js.adsonar.com/js/adsonar.js"></script>
...[SNIP]...
</script>
<script language="JavaScript" src="http://js.adsonar.com/js/adsonar.js"></script>
...[SNIP]...
</div>

<script language="Javascript1.1" SRC="http://o.aolcdn.com/ads/adsEnd.js"></script>
...[SNIP]...
5. Email addresses disclosed  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.dailyfinance.com
Path:   /quotes/linear-technology-corporation/lltc/nas

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 /quotes/linear-technology-corporation/lltc/nas HTTP/1.1
Host: www.dailyfinance.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 16:46:41 GMT
Server: Apache
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0, must-revalidate, proxy-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Set-Cookie: IPHONE_MESSAGE=2; Expires=Mon, 14-Feb-2011 16:46:41 GMT; Path=/
Content-Language: en
Content-Length: 176464
Keep-Alive: timeout=5, max=991
Connection: Keep-Alive
Content-Type: text/html;charset=utf-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>LLTC: LINEAR TECHNOL
...[SNIP]...
<a href="mailto:MoneyComments@aol.com">
...[SNIP]...
Report generated by XSS.CX at Tue Nov 16 10:52:06 CST 2010.