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

Report generated by XSS.Cx at Mon Jan 23 12:19:33 CST 2012.

1. Cross-site scripting (reflected)

2. Cookie without HttpOnly flag set

2.1. http://www.avangate.com/online-payment-solutions/

2.2. http://www.avangate.com/search/

3. Password field with autocomplete enabled

3.1. http://www.avangate.com/login/

3.2. http://www.avangate.com/login/

3.3. http://www.avangate.com/login/

3.4. http://www.avangate.com/login/

4. Cross-domain Referer leakage

5. Email addresses disclosed

1. Cross-site scripting (reflected) next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/search/

Issue detail

The value of the q request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %003142f"><script>alert(1)</script>70c483bf421 was submitted in the q parameter. This input was echoed as 3142f"><script>alert(1)</script>70c483bf421 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 application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of 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 /search/?q=checkout+credit+card%003142f"><script>alert(1)</script>70c483bf421&go.x=0&go.y=0 HTTP/1.1
Host: www.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
Proxy-Connection: keep-alive
Referer: http://www.avangate.com/company/about.php
Cookie: PHPSESSID=78fbc8b158895d941de8c5e68f4a4868; s_cc=true; s_sq=gecadavangatewebsite%3D%2526pid%253Dhttp%25253A//www.avangate.com/company/about.php%2526pidt%253D1%2526oid%253Dhttp%25253A//cdn.avangate.com/web/docs/en/design/1x1.gif%25253F20091019100706%2526ot%253DIMAGE
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:51:44 GMT
Server: Apache
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
Vary: Accept-Encoding,User-Agent
Content-Length: 38611
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...
<a class="pagination_link" href="?q=checkout credit card.3142f"><script>alert(1)</script>70c483bf421&lr=lang_en&p=2">
...[SNIP]...

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

/online-payment-solutions/
/search/

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.

2.1. http://www.avangate.com/online-payment-solutions/ next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.avangate.com
Path:	/online-payment-solutions/

Issue detail

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

PHPSESSID=6ffe4f81ed6ae8ece3cd748171de4d3d; 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.

Request

GET /online-payment-solutions/ HTTP/1.1
Host: www.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
Proxy-Connection: keep-alive
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:50:18 GMT
Server: Apache
Set-Cookie: PHPSESSID=6ffe4f81ed6ae8ece3cd748171de4d3d; 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
Vary: Accept-Encoding,User-Agent
Content-Length: 61372
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

2.2. http://www.avangate.com/search/ previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.avangate.com
Path:	/search/

Issue detail

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

PHPSESSID=6ac9f3d76a7117117ac783779464d476; 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.

Request

GET /search/?q=checkout+credit+card%003142f%22%3E%3Cscript%3Eprompt(document.location)%3C/script%3E70c483bf421&go.x=0&go.y=0 HTTP/1.1
Host: www.avangate.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Accept: */*
Referer: http://www.avangate.com/search/?q=checkout+credit+card%003142f%22%3E%3Cscript%3Eprompt(document.location)%3C/script%3E70c483bf421&go.x=0&go.y=0
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: s_cc=true; s_sq=%5B%5BB%5D%5D
Content-Length: 10

Response

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

/login/
/login/
/login/
/login/

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

3.1. http://www.avangate.com/login/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/login/

Issue detail

The page contains a form with the following action URL:

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

The form contains the following password field with autocomplete enabled:

password

Request

GET /login/ HTTP/1.1
Host: www.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
Proxy-Connection: keep-alive
Referer: http://www.avangate.com/search/?q=checkout+credit+card&go.x=0&go.y=0
Cookie: PHPSESSID=78fbc8b158895d941de8c5e68f4a4868; s_cc=true; s_sq=%5B%5BB%5D%5D; __switchTo5x=75; __unam=ecf86e9-134a4449d2f-616a9f72-1
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:51:26 GMT
Server: Apache
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
Vary: Accept-Encoding,User-Agent
Content-Length: 44909
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

                   <form action="https://secure.avangate.com/cpanel/login.php" id="form_vendor" class="signup-form" method="post">
                       <table border="0" cellpadding="0" cellspacing="0" width="100%">
...[SNIP]...
<td colspan="2">
                                                       <input class="text" style=" border: 1px solid #7F9DB9; height: 20px; padding: 2px; width: 210px;" id="password" name="password" onblur="if(this.value == '') { this.value='******';this.style.color=''; }" onfocus="if (this.value == '******') {this.value='';this.style.color='black';};" type="password" value="******" /></td>
...[SNIP]...

3.2. http://www.avangate.com/login/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/login/

Issue detail

The page contains a form with the following action URL:

https://secure.avangate.com/affiliates/login.php

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:51:26 GMT
Server: Apache
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
Vary: Accept-Encoding,User-Agent
Content-Length: 44909
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

                   <form action="https://secure.avangate.com/affiliates/login.php" id="form_affiliate" method="post" class="signup-form">
                       <table border="0" cellpadding="0" cellspacing="0" width="100%">
...[SNIP]...
<td colspan="2">
                                                       <input class="text" id="password" style=" border: 1px solid #7F9DB9; height: 20px; padding: 2px; width: 210px;" name="password" onblur="if(this.value == '') { this.value='******';this.style.color=''; }" onfocus="if (this.value == '******') {this.value='';this.style.color='black';};" type="password" value="******" /></td>
...[SNIP]...

3.3. http://www.avangate.com/login/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/login/

Issue detail

The page contains a form with the following action URL:

https://secure.avangate.com/myaccount/

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:51:26 GMT
Server: Apache
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
Vary: Accept-Encoding,User-Agent
Content-Length: 44909
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

                   <form action="https://secure.avangate.com/myaccount/" id="form_shopper" method="post" class="signup-form">
                       <table border="0" cellpadding="0" cellspacing="0" width="100%">
...[SNIP]...
<td colspan="2">
                                                       <input class="text" id="password" style=" border: 1px solid #7F9DB9; height: 20px; padding: 2px; width: 210px;" name="password" onblur="if(this.value == '') { this.value='******';this.style.color=''; }" onfocus="if (this.value == '******') {this.value='';this.style.color='black';};" type="password" value="******" /></td>
...[SNIP]...

3.4. http://www.avangate.com/login/ previous

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/login/

Issue detail

The page contains a form with the following action URL:

https://arms.avangate.com/partners/

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 15:51:26 GMT
Server: Apache
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
Vary: Accept-Encoding,User-Agent
Content-Length: 44909
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

                   <form action="https://arms.avangate.com/partners/" id="form_arms_partner" method="post" name="arms-form" class="signup-form">
                       <table border="0" cellpadding="0" cellspacing="0" width="100%">
...[SNIP]...
<td colspan="2">
                                                       <input class="text" id="password" style=" border: 1px solid #7F9DB9; height: 20px; padding: 2px; width: 210px;" name="password" onblur="if(this.value == '') { this.value='******';this.style.color=''; }" onfocus="if (this.value == '******') {this.value='';this.style.color='black';};" type="password" value="******" /></td>
...[SNIP]...

4. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/search/

Issue detail

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

http://www.avangate.com/search/?q=checkout+credit+card%003142f%22%3E%3Cscript%3Eprompt(document.location)%3C/script%3E70c483bf421&go.x=0&go.y=0

The response contains the following links to other domains:

http://feeds.feedburner.com/Avangate-News
http://feeds.feedburner.com/Software-Affiliate-Marketing
http://feeds.feedburner.com/Software-Business
http://gecadavangatewebsite.122.2o7.net/b/ss/gecadavangatewebsite/1/H.20.3--NS/0
http://sanjose.bbb.org/BusinessReport.aspx?CompanyID=244636&source=ctc
http://twitter.com/Avangate
http://vlog.leadformix.com/bf/bf.php
http://www.facebook.com/avangate
http://www.flickr.com/photos/avangate
http://www.leadformix.com/
http://www.linkedin.com/company/1216161
http://www.omniture.com/
https://seal.verisign.com/splash?form_file=fdf/splash.fdf&dn=SECURE.AVANGATE.COM&lang=en
https://www.pcisecuritystandards.org/
https://www.scanalert.com/RatingVerify?ref=secure.avangate.com

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
Date: Mon, 23 Jan 2012 17:47:39 GMT
Server: Apache
Set-Cookie: PHPSESSID=6ac9f3d76a7117117ac783779464d476; 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
Vary: Accept-Encoding,User-Agent
Content-Length: 41702
Content-Type: text/html

<!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">
<head>
<meta http-equiv="Content-T
...[SNIP]...

<link rel="alternate" type="application/rss+xml" title="RSS - Software Business" href="http://feeds.feedburner.com/Software-Business" />
<link rel="alternate" type="application/rss+xml" title="RSS - Affiliate Marketing" href="http://feeds.feedburner.com/Software-Affiliate-Marketing" />
<link rel="alternate" type="application/rss+xml" title="RSS - Industry News from Avangate" href="http://feeds.feedburner.com/Avangate-News" />

</head>
...[SNIP]...
<div class="next_steps_link">
<a href="http://www.facebook.com/avangate" target="_blank"><img class="new-sprite f-icon-facebook f-icon-facebook-hover" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Connect with Avangate on Facebook" title="Join us on Facebook"
...[SNIP]...
</a>
<a href="http://www.facebook.com/avangate" target="_blank" title="Join us on Facebook" style="margin-left:10px;">Join us on Facebook</a>
...[SNIP]...
<div class="next_steps_link">
<a href="http://www.linkedin.com/company/1216161" target="_blank"><img class="new-sprite f-icon-linkedin f-icon-linkedin-hover" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Avangate on Linkedin" title="Avangate on Linkedin" /></a>
<a href="http://www.linkedin.com/company/1216161" target="_blank" title="Avangate on Linkedin" style="margin-left:10px;">Join our group</a>
...[SNIP]...
<div class="next_steps_link">
<a href="http://twitter.com/Avangate" target="_blank"><img class="new-sprite f-icon-twitter f-icon-twitter-hover" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Follow Avangate on Twitter" title="Follow Avangate on Twitter" /
...[SNIP]...
</a>
<a href="http://twitter.com/Avangate" title="Follow Avangate on Twitter" target="_blank" style="margin-left:10px;">Follow us</a>
...[SNIP]...
<div class="next_steps_link">
<a href="http://www.flickr.com/photos/avangate" target="_blank"><img class="new-sprite f-icon-flickr f-icon-flickr-hover" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="See our pictures" title="See our pictures" /></a>
<a href="http://www.flickr.com/photos/avangate" title="See our pictures" style="margin-left:10px;" target="_blank">See our pictures</a>
...[SNIP]...
<td>
<a href="https://seal.verisign.com/splash?form_file=fdf/splash.fdf&dn=SECURE.AVANGATE.COM&lang=en" onclick="window.open(this.href,'verysignwin', 'toolbar=no,location=no,directories=no,status=yes,menubar=no,scrollbars=no,resizable=no,width=550,height=566');return false;"><img class="sprite verisign" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Click to verify" title="Click to verify" /></a>
<a target="_blank" href="https://www.scanalert.com/RatingVerify?ref=secure.avangate.com"><img class="sprite hackersafe" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="HACKER SAFE certified sites prevent over 99.9% of hacker crime." />
...[SNIP]...
<br />
<a href="https://www.pcisecuritystandards.org/" title="PCI Security Standards Council"><img class="sprite pci" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="PCI Security Standards Council" />
...[SNIP]...
<td>
<a href="http://sanjose.bbb.org/BusinessReport.aspx?CompanyID=244636&source=ctc"><img class="sprite bbs" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="" title="" />
...[SNIP]...
<td style="padding-left:0px;"><a href="http://www.facebook.com/avangate"><img class="new-sprite f-icon-facebook" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Connect with Avangate on Facebook" title="Connect with Avangate on Facebook" />
...[SNIP]...
<td><a href="http://twitter.com/Avangate"><img class="new-sprite f-icon-twitter" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Follow Avangate on Twitter" title="Follow Avangate on Twitter" />
...[SNIP]...
<td><a href="http://www.flickr.com/photos/avangate"><img class="new-sprite f-icon-flickr" src="http://cdn.avangate.com/web/docs/en/design/1x1.gif?20091019100706" alt="Avangate on Flickr" title="Avangate on Flickr" />
...[SNIP]...
<noscript><a href="http://www.omniture.com" title="Web Analytics">
<img
src="http://gecadavangatewebsite.122.2O7.net/b/ss/gecadavangatewebsite/1/H.20.3--NS/0"
height="1" width="1" border="0" alt="" /></a>
...[SNIP]...

<a href="http://www.leadformix.com" title="Marketing Automation" onclick="window.open(this.href);return(false);">
<script type="text/javascript">
...[SNIP]...
<p>Market analytics <img src="http://vlog.leadformix.com/bf/bf.php" style="border:0" alt="bf"/></p>
...[SNIP]...

5. Email addresses disclosed previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.avangate.com
Path:	/search/

Issue detail

The following email address was disclosed in the response:

support@avangate.com

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

Response

Report generated by XSS.Cx at Mon Jan 23 12:19:33 CST 2012.