The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 8ce48<script>alert(1)</script>57aff9187ec was submitted in the callback 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.
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
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.
HTTP/1.1 200 OK Cache-Control: private,max-age=0 Content-Type: text/javascript; charset=utf-8 Expires: Wed, 01 Jan 1997 12:00:00 GMT Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:32:02 GMT Content-Length: 71
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.
Common explanations for Referer-dependent responses include:
Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.
Issue remediation
The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.
If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=8975%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:56 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script type="text/javascript" language="javascript" src="http://img3.wsimg.com/pc/js/1/gd_js_20110203.min.js"></script> <script type="text/javascript"> var pcj_pl_id = "1"; var pcj_url_help = "http://help.godaddy.com/"; var pcj_url_bp = "http://www.bobparsons.me/"; var pcj_args = "?ci="; var pcj_url_cmnty= "http://community.godaddy.com/"; var pcj_url_mya="https://mya.godaddy.com/"; var pcj_url_sales = "http://www.godaddy.com/"; var pcj_url_img = "http://img1.wsimg.com/"; var pcj_idpredirect = ""; var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_isCmnty = false; var pcj_cname = "ShopperId1"; var pcj_cdomain = ".godaddy.com"; var pcj_callov = false; var pcj_call = true; var pct_loginnameDone = false; var pct_loginnameField; var pcj_login_root_url="https://idp.godaddy.com/login.aspx?ci=9106&spkey=GDSWNET-M1PWCORPWEB103"; var pcj_navnm = "sales"; var pcj_phoneflags = "uk|ie|nl|fr|it|es|de|au";
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=8975%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:32:00 GMT Content-Length: 134715
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script type="text/javascript" language="javascript" src="http://img3.wsimg.com/pc/js/1/gd_js_20110203.min.js"></script> <script type="text/javascript"> var pcj_pl_id = "1"; var pcj_url_help = "http://help.godaddy.com/"; var pcj_url_bp = "http://www.bobparsons.me/"; var pcj_args = "?ci="; var pcj_url_cmnty= "http://community.godaddy.com/"; var pcj_url_mya="https://mya.godaddy.com/"; var pcj_url_sales = "http://www.godaddy.com/"; var pcj_url_img = "http://img1.wsimg.com/"; var pcj_idpredirect = ""; var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_isCmnty = false; var pcj_cname = "ShopperId1"; var pcj_cdomain = ".godaddy.com"; var pcj_callov = false; var pcj_call = true; var pct_loginnameDone = false; var pct_loginnameField; var pcj_login_root_url="https://idp.godaddy.com/login.aspx?ci=9106&spkey=GDSWNET-M1PWCORPWEB103"; var pcj_navnm = "sales"; var pcj_phoneflags = "uk|ie|nl|fr|it|es|de|au";
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 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 /default.aspx HTTP/1.1 Host: www.godaddy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: flag1=cflag=us; currency1=potableSourceStr=USD; currencypopin1=cdisplaypopin=false; ShopperId1=aabdeikhidaanjedjbmdbbuhxjrjqdfj; visitor=vid=c46d38ed-6ae8-4ddf-9d53-4f7b0b891348
Response
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 Set-Cookie: ASP.NET_SessionId=vyantv55ubkvkh45jzvwp455; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: adc1=US; domain=godaddy.com; path=/ Set-Cookie: SplitValue1=79; domain=godaddy.com; expires=Fri, 25-Mar-2011 17:30:52 GMT; path=/ Set-Cookie: traffic=cookies=1&referrer=&sitename=www.godaddy.com&page=/default.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=&referringdomain=&split=79; domain=godaddy.com; path=/ Set-Cookie: Domainer1=false; domain=godaddy.com; expires=Sun, 27-Mar-2011 17:30:52 GMT; path=/ Set-Cookie: GoogleADServicesgoogleadwordshome=mjlbzbgdjajjcimhpgtgkbjeijwdcefe; domain=godaddy.com; expires=Wed, 24-Mar-2021 17:30:52 GMT; path=/ Set-Cookie: HPBackground=DanicaImageOne; path=/ Set-Cookie: HPBackground=DanicaImageOne; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:52 GMT Content-Length: 245019
<!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.
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<link rel="canonical" href="http://www.godaddy.com/hosting/website-builder.aspx"/> ...[SNIP]... <meta name="keywords" content="website builder, how to make a Web site, create a Web site, make a Web site, make your own Web site, Go Daddy.com, Go Daddy, godaddy.com, godaddy" /><link rel="shortcut icon" href="http://img1.wsimg.com/assets/godaddy.ico" /></head> <body id="ctl00_PageBody" style="width:100%;margin:0;">
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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 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 /default.aspx HTTP/1.1 Host: www.godaddy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: flag1=cflag=us; currency1=potableSourceStr=USD; currencypopin1=cdisplaypopin=false; ShopperId1=aabdeikhidaanjedjbmdbbuhxjrjqdfj; visitor=vid=c46d38ed-6ae8-4ddf-9d53-4f7b0b891348
Response
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 Set-Cookie: ASP.NET_SessionId=vyantv55ubkvkh45jzvwp455; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: adc1=US; domain=godaddy.com; path=/ Set-Cookie: SplitValue1=79; domain=godaddy.com; expires=Fri, 25-Mar-2011 17:30:52 GMT; path=/ Set-Cookie: traffic=cookies=1&referrer=&sitename=www.godaddy.com&page=/default.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=&referringdomain=&split=79; domain=godaddy.com; path=/ Set-Cookie: Domainer1=false; domain=godaddy.com; expires=Sun, 27-Mar-2011 17:30:52 GMT; path=/ Set-Cookie: GoogleADServicesgoogleadwordshome=mjlbzbgdjajjcimhpgtgkbjeijwdcefe; domain=godaddy.com; expires=Wed, 24-Mar-2021 17:30:52 GMT; path=/ Set-Cookie: HPBackground=DanicaImageOne; path=/ Set-Cookie: HPBackground=DanicaImageOne; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:52 GMT Content-Length: 245019
<!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.
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=cookies=1&referrer=http://www.godaddy.com/default.aspx&sitename=www.godaddy.com&page=/hosting/website-builder.aspx&server=M1PWCORPWEB103&status=200 OK&querystring=ci=9028%26hpGoogleStatic%3d1&shopper=42533607&privatelabelid=1&isc=&clientip=173.193.214.243&referringpath=864f4225-b8c7-4647-893a-c28f3d3876fc&referringdomain=&split=11; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Thu, 24 Mar 2011 17:30:37 GMT Content-Length: 134768
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">