XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, console.iservices.net.nz

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d729d"><script>alert(1)</script>1478c083729 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.

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.

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.

Request

GET /?d729d"><script>alert(1)</script>1478c083729=1 HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.0 200 OK
Date: Sun, 15 May 2011 17:33:41 GMT
Server: Apache
X-Powered-By: PHP/5.3.0
Set-Cookie: ISERVICES_SESSID=ITTEbbftfdQKVOjeNFZcc8YO4shpEO9; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8

<!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">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
<input type="hidden" name="d729d"><script>alert(1)</script>1478c083729" value="1" />
...[SNIP]...

2. Flash cross-domain policy previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which allows access from any domain.

Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.

Issue background

The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.

Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.

Issue remediation

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

Request

GET /crossdomain.xml HTTP/1.0
Host: console.iservices.net.nz

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 17:33:30 GMT
Server: Apache
Last-Modified: Sat, 29 May 2010 23:33:46 GMT
ETag: "5c820f-c9-487c40e0e4a80"
Accept-Ranges: bytes
Content-Length: 201
Connection: close
Content-Type: text/xml

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
</cross-domain-policy>
...[SNIP]...

3. SSL cookie without secure flag set previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

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

ISERVICES_SESSID=a9agNSGwK4OtskHsxPBzoteywVW5xym; path=/

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

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

4. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

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

ISERVICES_SESSID=a9agNSGwK4OtskHsxPBzoteywVW5xym; path=/

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

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.

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

5. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The page contains a form with the following action URL:

https://console.iservices.net.nz/account/login/

The form contains the following password field with autocomplete enabled:

parameters[password]

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).

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.0 200 OK
Date: Sun, 15 May 2011 17:33:28 GMT
Server: Apache
X-Powered-By: PHP/5.3.0
Set-Cookie: ISERVICES_SESSID=a9agNSGwK4OtskHsxPBzoteywVW5xym; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8

<!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">
   <head>
       <meta http-equiv="Content-Type" cont
...[SNIP]...
<div style="display: ;" id="divLogin">
   <form action="/account/login/" method="post" style="display: inline;" name="loginForm">
                                       <table width="100%" border="0" cellspacing="0" cellpadding="0">
...[SNIP]...
<td colspan="2" class="dataTableMainCell" style="padding: 5px 5px 5px 25px;">
                   <input name="parameters[password]" type="password" style="width: 200px;" tabindex="2"><br />
...[SNIP]...

6. Cross-domain POST previous next
There are 2 instances of this issue:

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.

6.1. https://console.iservices.net.nz/ next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The page contains a form which POSTs data to the domain orcres.cosmos.net.nz. The form contains the following fields:

username
password
failureurl

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.0 200 OK
Date: Sun, 15 May 2011 17:33:28 GMT
Server: Apache
X-Powered-By: PHP/5.3.0
Set-Cookie: ISERVICES_SESSID=a9agNSGwK4OtskHsxPBzoteywVW5xym; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8

<!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">
   <head>
       <meta http-equiv="Content-Type" cont
...[SNIP]...
</p>
                                   <form id="account" name="accountlogin" action="https://orcres.cosmos.net.nz/orconmembersarea.php" method="post" autocomplete="off">
                                       <fieldset>
...[SNIP]...

6.2. https://console.iservices.net.nz/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The page contains a form which POSTs data to the domain www.orcon.net.nz. The form contains the following fields:

ACT
XID
RP
NRP
RES
status
weblog
search_in
where
site_id
keywords
submit

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.0 200 OK
Date: Sun, 15 May 2011 17:33:28 GMT
Server: Apache
X-Powered-By: PHP/5.3.0
Set-Cookie: ISERVICES_SESSID=a9agNSGwK4OtskHsxPBzoteywVW5xym; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8

<!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">
   <head>
       <meta http-equiv="Content-Type" cont
...[SNIP]...
</a>
                       <form id='site-search' name='site-search' method="post" action="http://www.orcon.net.nz/index.php" >
<div class='hiddenFields'>
...[SNIP]...

7. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The response dynamically includes the following script from another domain:

https://www.orcon.net.nz/external/prequal/websitetools-v1.1.js?20100406_13

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 / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

8. TRACE method is enabled previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: console.iservices.net.nz
Cookie: a98c30c650d097a6

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 17:33:29 GMT
Server: Apache
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: console.iservices.net.nz
Cookie: a98c30c650d097a6

9. Email addresses disclosed previous next
There are 2 instances of this issue:

/
/scripts/jquery.pngFix.pack.js

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).

9.1. https://console.iservices.net.nz/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The following email address was disclosed in the response:

hostingsales@orcon.net.nz

Request

GET / HTTP/1.1
Host: console.iservices.net.nz
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

9.2. https://console.iservices.net.nz/scripts/jquery.pngFix.pack.js previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/scripts/jquery.pngFix.pack.js

Issue detail

The following email address was disclosed in the response:

andreas.eberhard@gmail.com

Request

GET /scripts/jquery.pngFix.pack.js HTTP/1.1
Host: console.iservices.net.nz
Connection: keep-alive
Referer: https://console.iservices.net.nz/?d729d%22%3E%3Cscript%3Ealert(%22GHDB%22)%3C/script%3E1478c083729=1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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: ISERVICES_SESSID=NHUT4dtoCqXuGqUoMyueYNv3LO8OAvJ

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 17:36:27 GMT
Server: Apache
Last-Modified: Sat, 29 May 2010 23:33:47 GMT
ETag: "5d0a51-9bf-487c40e1d8cc0"
Accept-Ranges: bytes
Content-Length: 2495
Connection: close
Content-Type: application/x-javascript

/**
* --------------------------------------------------------------------
* jQuery-Plugin "pngFix"
* Version: 1.1, 11.09.2007
* by Andreas Eberhard, andreas.eberhard@gmail.com
* http://jquery.andreaseberhard.de/
*
* Copyright (c) 2007 Andreas Eberhard
* Licensed under GPL (http://www.opensource.org/licenses/gpl-license.php)
*/
eval(function(p
...[SNIP]...

10. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/favicon.ico

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

Request

GET /favicon.ico HTTP/1.1
Host: console.iservices.net.nz
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Accept: image/png,image/*;q=0.8,*/*;q=0.5
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
Cookie: ISERVICES_SESSID=NHUT4dtoCqXuGqUoMyueYNv3LO8OAvJ

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 17:57:43 GMT
Server: Apache
Last-Modified: Sat, 29 May 2010 23:33:46 GMT
ETag: "5c8220-47e-487c40e0e4a80"
Accept-Ranges: bytes
Content-Length: 1150
Connection: close
Content-Type: text/plain; charset=UTF-8

............ .h.......(....... ..... ....................................................PC.9.C.9....P...........................................0^LU.)...)...)...)...^LU....0..........................
...[SNIP]...

11. Content type incorrectly stated previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	https://console.iservices.net.nz
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=UTF-8

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

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

Response

12. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://console.iservices.net.nz
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	console.iservices.net.nz
Issued by:	UTN-USERFirst-Hardware
Valid from:	Sun Aug 01 19:00:00 CDT 2010
Valid to:	Thu Sep 22 18:59:59 CDT 2011

Certificate chain #1

Issued to:	UTN-USERFirst-Hardware
Issued by:	AddTrust External CA Root
Valid from:	Tue Jun 07 03:09:10 CDT 2005
Valid to:	Sat May 30 05:48:38 CDT 2020

Certificate chain #2

Issued to:	AddTrust External CA Root
Issued by:	AddTrust External CA Root
Valid from:	Tue May 30 05:48:38 CDT 2000
Valid to:	Sat May 30 05:48:38 CDT 2020

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by XSS.CX at Sun May 15 14:48:09 CDT 2011.