UnsafeWindow: Difference between revisions

From GreaseSpot Wiki
Jump to navigationJump to search
← Older edit
No edit summary
simple formatting
 
(151 intermediate revisions by 21 users not shown)
Line 1: Line 1:
{{lowercase}}
{{DISPLAYTITLE:unsafeWindow}}
{{security}}
{{security}}


= Syntax =
== Description ==


'''unsafeWindow'''
This object allows a [[User script]] to access "custom" properties set by the web page.
The user script is otherwise isolated from these properties.


= Description =
:*'''USE OF UNSAFEWINDOW IS INSECURE, AND IT SHOULD BE AVOIDED WHENEVER POSSIBLE.'''


[[User script]]s can use this object to access "custom" properties--variable and functions defined in the page--set by the web page.
unsafeWindow bypasses [[Greasemonkey]]'s security model, which exists to make sure that malicious web pages cannot alter objects in such a way as to make user scripts (which execute with more privileges than ordinary JavaScript running in a web page) do things that their authors or users did not intend.
This is done by bypassing [[Greasemonkey]]'s [[XPCNativeWrapper]]-based [[security]] model.
User scripts should therefore avoid calling or in any other way depending on any properties on unsafeWindow - especially if they are executed for arbitrary web pages, such as those with <code>@[[Include and exclude rules|include]] *</code>.
The unsafeWindow object is shorthand for window.wrappedJSObject; it is the raw window object inside the XPCNativeWrapper provided by the Greasemonkey [[sandbox]].


Use of unsafeWindow is insecure, and it should be avoided whenever possible.
== Examples ==
User scripts absolutely should not use unsafeWindow if they are executed for arbitrary web pages, such as those with <code>@[[Include and exclude rules|include]] *</code>.
[[User script]] authors are '''strongly''' encouraged to learn how [[XPCNativeWrapper]]s work, and how to perform the desired function within their security context, instead of using unsafeWindow to break out.


= Examples =
<pre class='sample-bad'>
unsafeWindow.SomeVarInPage = "Testing";
</pre>


unsafeWindow.SomeVarInPage = "Testing";
<pre class='sample-bad'>
unsafeWindow.SomeFunctionInPage("Test");
</pre>


unsafeWindow.SomeFunctionInPage("Test");
<pre class='sample-bad'>
var oldFunction = unsafeWindow.SomeFunctionInPage;
unsafeWindow.SomeFunctionInPage = function(text) {
  alert('Hijacked! Argument was ' + text + '.');
  return oldFunction(text);
};
</pre>


var oldFunction = unsafeWindow.SomeFunctionInPage;
== Alternatives to unsafeWindow ==
unsafeWindow.SomeFunctionInPage = function(text) {
  alert("Hijacked! Argument was " + text + ".");
  return oldFunction(text);
}


= Alternatives to unsafeWindow =
''Sometimes'', you just can't get around using unsafeWindow.
Most of the time, however, you can!
See [[:Category:Coding Tips:Interacting With The Page]] for details on various methods to interact with the page that do '''not''' use unsafeWindow.


== Events ==
[[Category:API_Reference|U]]  
 
[[Category:Scripting context]]
Event listeners never need to be created on unsafeWindow. Rather than using <code>unsafeWindow.onclick = function(event) { ... }</code>, use:
[[Category:Security]]
 
window.addEventListener('click', function(event) {
  ...
}, false);
 
[http://developer.mozilla.org/en/docs/DOM:element.addEventListener addEventListener at MDC]
 
== Functions defined in the page ==
 
If a user script must execute a page function, it can use the '''[[location hack]]''' to call it safely. This involves setting location.href to a <code>javascript:</code> URL, which is like using a bookmarklet. For example:
 
location.href = 'javascript:void(pageFunc(123));';
 
Larger blocks of code can also be executed this way:
 
location.href = 'javascript:(' + encodeURI(uneval(function() {
  // some code
})) + ')();';
 
This code will run in the page context without leaking the [[sandbox]]. This code is completely separate from the rest of the script scope, sometimes limiting its usefulness. For example, data cannot be returned by the function.
 
Another drawback is that this technique is rather ugly. Still, it is preferred over unsafeWindow.
 
 
[[Category:API Reference|U]]

Latest revision as of 14:15, 11 March 2023

This command can open certain security holes in your user script, and it is recommended to use this command sparingly.

Please be sure to read the entire article and understand it before using it in a script.


Description

This object allows a User script to access "custom" properties set by the web page. The user script is otherwise isolated from these properties.

  • USE OF UNSAFEWINDOW IS INSECURE, AND IT SHOULD BE AVOIDED WHENEVER POSSIBLE.

unsafeWindow bypasses Greasemonkey's security model, which exists to make sure that malicious web pages cannot alter objects in such a way as to make user scripts (which execute with more privileges than ordinary JavaScript running in a web page) do things that their authors or users did not intend. User scripts should therefore avoid calling or in any other way depending on any properties on unsafeWindow - especially if they are executed for arbitrary web pages, such as those with @include *.

Examples

unsafeWindow.SomeVarInPage = "Testing";

unsafeWindow.SomeFunctionInPage("Test");

var oldFunction = unsafeWindow.SomeFunctionInPage;
unsafeWindow.SomeFunctionInPage = function(text) {
  alert('Hijacked! Argument was ' + text + '.');
  return oldFunction(text);
};

Alternatives to unsafeWindow

Sometimes, you just can't get around using unsafeWindow. Most of the time, however, you can! See Category:Coding Tips:Interacting With The Page for details on various methods to interact with the page that do not use unsafeWindow.

Retrieved from "https://wiki.greasespot.net/index.php?title=UnsafeWindow&oldid=7923"