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 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.
1.1. http://sharepoint.microsoft.com/ScriptResource.axd [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/ScriptResource.axd
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bc6ab'-alert(1)-'b98324afb87 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 99826 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:33 GMT Last-Modified: Tue, 02 Aug 2011 16:53:33 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:32 GMT
var waxMagic=function(){ if(typeof($create)=='undefined')$create=undefined;if(typeof($addHandler)=='undefined')$addHandler=undefined;if(typeof($addHandlers)=='undefined')$addHandlers=undefined;if(typ ...[SNIP]... I||WAX_RI('/ScriptResource.axd?d=UeSdpXH5xa9ZIvLjPIuIEbiagmkNWBOlzOGH-YBHy5QVnh_OteDkpqSVIen9ZZ0chXeeQLILpN2CEQ1NHqSBGhsOkRZL4olhbt9ywp82pyYbz8lIjz3jY1rT7HPPCN40eb1vMWYw94EAPq5LT0vGExGfwKE1&t=5c2f384e&bc6ab'-alert(1)-'b98324afb87=1',waxMagic))waxMagic();
The value of the t request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 74a7f'-alert(1)-'1ca200cf3ce 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 99823 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:27 GMT Last-Modified: Tue, 02 Aug 2011 16:53:27 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:27 GMT
var waxMagic=function(){ if(typeof($create)=='undefined')$create=undefined;if(typeof($addHandler)=='undefined')$addHandler=undefined;if(typeof($addHandlers)=='undefined')$addHandlers=undefined;if(typ ...[SNIP]... RI||WAX_RI('/ScriptResource.axd?d=UeSdpXH5xa9ZIvLjPIuIEbiagmkNWBOlzOGH-YBHy5QVnh_OteDkpqSVIen9ZZ0chXeeQLILpN2CEQ1NHqSBGhsOkRZL4olhbt9ywp82pyYbz8lIjz3jY1rT7HPPCN40eb1vMWYw94EAPq5LT0vGExGfwKE1&t=5c2f384e74a7f'-alert(1)-'1ca200cf3ce',waxMagic))waxMagic();
1.3. http://sharepoint.microsoft.com/WebResource.axd [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/WebResource.axd
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e7b13'-alert(1)-'9c4f81ae0fd 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.
The value of the t request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c7715'-alert(1)-'8d28fe874dd 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.
1.5. http://sharepoint.microsoft.com/_layouts/1033/core.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/1033/core.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ac719'-alert(1)-'21b79887488 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e40ca'-alert(1)-'cd85ae552c2 was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 255471 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:56 GMT Last-Modified: Sat, 27 Mar 2010 04:45:56 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:55 GMT
var waxMagic=function(){ if(typeof(IsMenuShown)=='undefined')IsMenuShown=undefined;if(typeof(ChevronContainer)=='undefined')ChevronContainer=undefined;if(typeof(itemTableDeferred)=='undefined')itemTa ...[SNIP]... ;typeof NotifyScriptLoadedAndExecuteWaitingJobs=="function"&&NotifyScriptLoadedAndExecuteWaitingJobs("core.js") }; if(!window.WAX_RI||WAX_RI('/_layouts/1033/core.js?rev=c3ROI4x%2BKHVTMbn4JuFndQ%3D%3De40ca'-alert(1)-'cd85ae552c2',waxMagic))waxMagic();
1.7. http://sharepoint.microsoft.com/_layouts/1033/init.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/1033/init.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a80c6'-alert(1)-'9e6f3b4a90e 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e2014'-alert(1)-'6321ed85dfd was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 128388 Content-Type: application/x-javascript;charset=utf-8 Expires: Mon, 31 Oct 2011 16:53:32 GMT Last-Modified: Sat, 27 Mar 2010 04:45:56 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:31 GMT
var waxMagic=function(){ if(typeof(L_Infobar_Send_Error_Text)=='undefined')L_Infobar_Send_Error_Text=undefined;if(typeof(ULS)=='undefined')ULS=undefined;if(typeof(browseris)=='undefined')browseris=un ...[SNIP]... d"&&Sys&&Sys.Application&&Sys.Application.notifyScriptLoaded();NotifyScriptLoadedAndExecuteWaitingJobs("init.js") }; if(!window.WAX_RI||WAX_RI('/_layouts/1033/init.js?rev=BJDmyeIV5jS04CPkRq4Ldg%3D%3De2014'-alert(1)-'6321ed85dfd',waxMagic))waxMagic();
1.9. http://sharepoint.microsoft.com/_layouts/ScriptResx.ashx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/ScriptResx.ashx
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a41d7'-alert(1)-'89d46a8f299 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 14507 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:54:00 GMT Last-Modified: Sat, 27 Mar 2010 04:29:00 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:59 GMT
var waxMagic=function(){ _EnsureJSNamespace('SP');SP.Res={lcid:'1033',autocompleteAccessibleMenuName:'Autocomplete Menu',autocompleteLoading:'Loading...',autocompleteListNotFound:'List Not Found.',au ...[SNIP]... 'undefined'&&Sys&&Sys.Application){Sys.Application.notifyScriptLoaded();} }; if(!window.WAX_RI||WAX_RI('/_layouts/ScriptResx.ashx?culture=en%2Dus&name=SP%2ERes&rev=b6%2FcRx1a6orhAQ%2FcF%2B0ytQ%3D%3D&a41d7'-alert(1)-'89d46a8f299=1',waxMagic))waxMagic();
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5461f'-alert(1)-'0a339be4db7 was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 14504 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:55 GMT Last-Modified: Sat, 27 Mar 2010 04:29:00 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:55 GMT
var waxMagic=function(){ _EnsureJSNamespace('SP');SP.Res={lcid:'1033',autocompleteAccessibleMenuName:'Autocomplete Menu',autocompleteLoading:'Loading...',autocompleteListNotFound:'List Not Found.',au ...[SNIP]... ='undefined'&&Sys&&Sys.Application){Sys.Application.notifyScriptLoaded();} }; if(!window.WAX_RI||WAX_RI('/_layouts/ScriptResx.ashx?culture=en%2Dus&name=SP%2ERes&rev=b6%2FcRx1a6orhAQ%2FcF%2B0ytQ%3D%3D5461f'-alert(1)-'0a339be4db7',waxMagic))waxMagic();
1.11. http://sharepoint.microsoft.com/_layouts/blank.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/blank.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 685b4'-alert(1)-'087ef22ff93 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c7279'-alert(1)-'bee140d5a1e was submitted in the rev 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.
1.13. http://sharepoint.microsoft.com/_layouts/cui.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/cui.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b847a'-alert(1)-'2cfd1ab224f 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload dce79'-alert(1)-'900baf67bb8 was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 351817 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:55 GMT Last-Modified: Thu, 28 Jan 2010 07:43:20 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:55 GMT
var waxMagic=function(){ if(typeof(IEnumerator)=='undefined')IEnumerator=undefined;if(typeof(IEnumerable)=='undefined')IEnumerable=undefined;if(typeof(g_cuiXMLDOMDocument)=='undefined')g_cuiXMLDOMDoc ...[SNIP]... Loaded();typeof NotifyScriptLoadedAndExecuteWaitingJobs!="undefined"&&NotifyScriptLoadedAndExecuteWaitingJobs("CUI.js") }; if(!window.WAX_RI||WAX_RI('/_layouts/cui.js?rev=wvoVpqlQb30nGo4DjDk8Kg%3D%3Ddce79'-alert(1)-'900baf67bb8',waxMagic))waxMagic();
1.15. http://sharepoint.microsoft.com/_layouts/inplview.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/inplview.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload fc6ce'-alert(1)-'b2c9a69c116 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e5f7f'-alert(1)-'6f836fe0ca5 was submitted in the rev 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.
1.17. http://sharepoint.microsoft.com/_layouts/mediaplayer.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/mediaplayer.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bef49'-alert(1)-'7d60c7b5c32 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b2de8'-alert(1)-'5ca5540d3fe was submitted in the rev 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.
1.19. http://sharepoint.microsoft.com/_layouts/sp.core.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/sp.core.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 572d2'-alert(1)-'028b9958eea 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5c2f9'-alert(1)-'dfd195e3d79 was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 12683 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:53:51 GMT Last-Modified: Sat, 27 Mar 2010 04:45:56 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:53:51 GMT
var waxMagic=function(){ if(typeof(IEnumerator)=='undefined')IEnumerator=undefined;if(typeof(IEnumerable)=='undefined')IEnumerable=undefined;if(typeof(IDisposable)=='undefined')IDisposable=undefined; ...[SNIP]... s&&Sys.Application&&Sys.Application.notifyScriptLoaded();NotifyScriptLoadedAndExecuteWaitingJobs("sp.core.js"); }; if(!window.WAX_RI||WAX_RI('/_layouts/sp.core.js?rev=7ByNlH%2BvcgRJg%2BRCctdC0w%3D%3D5c2f9'-alert(1)-'dfd195e3d79',waxMagic))waxMagic();
1.21. http://sharepoint.microsoft.com/_layouts/sp.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/sp.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 29636'-alert(1)-'e9c588154e 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ebde1'-alert(1)-'555525404b4 was submitted in the rev 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.
1.23. http://sharepoint.microsoft.com/_layouts/sp.ribbon.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/sp.ribbon.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5b5c4'-alert(1)-'99fa3ff5a0a 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 827f4'-alert(1)-'d0e186a3edb was submitted in the rev 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.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 212757 Content-Type: application/x-javascript;charset=utf-8 Expires: Tue, 02 Aug 2011 17:54:20 GMT Last-Modified: Sat, 27 Mar 2010 04:45:56 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 14.0.0.4762 S: AA11 Date: Tue, 02 Aug 2011 16:54:20 GMT
var waxMagic=function(){ if(typeof(ribbon)=='undefined')ribbon=undefined; ULS04Z=function(){var o=new Object;o.ULSTeamName="Microsoft SharePoint Foundation";o.ULSFileName="SP.Ribbon.js";return o;}; D ...[SNIP]... ifyScriptLoadedAndExecuteWaitingJobs("sp.ribbon.js");SP.Ribbon.TrackTabPageComponent.registerWithPageManager(); }; if(!window.WAX_RI||WAX_RI('/_layouts/sp.ribbon.js?rev=F%2BUEJ66rbXzSvpf7nN69wQ%3D%3D827f4'-alert(1)-'d0e186a3edb',waxMagic))waxMagic();
1.25. http://sharepoint.microsoft.com/_layouts/sp.runtime.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/sp.runtime.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 2f87b'-alert(1)-'aae618a98a5 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e8a84'-alert(1)-'470195b6182 was submitted in the rev 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.
1.27. http://sharepoint.microsoft.com/_layouts/sp.ui.dialog.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://sharepoint.microsoft.com
Path:
/_layouts/sp.ui.dialog.js
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload beec0'-alert(1)-'5b06df7b2ca 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.
The value of the rev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5b00f'-alert(1)-'da5ccae2563 was submitted in the rev 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.
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.