UnsafeWindow: Difference between revisions
m →Attach script to page: top/back anchors added |
m →Method 1: White space treatment |
||
Line 113: | Line 113: | ||
<code><pre> | <code><pre> | ||
function myScript() { | function myScript() { | ||
for(var x in document) { | for (var x in document) { | ||
// do something with x | // do something with x | ||
} | } | ||
// blah blah blah | |||
} | } | ||
// attach script to page; script can therefore reference variables on the page, but likewise | // attach script to page; script can therefore reference variables on the page, but likewise | ||
// cannot use greasemonkey API methods | // cannot use greasemonkey API methods | ||
document.body.appendChild(document.createElement("script")).innerHTML="("+myScript+")()"; | |||
document.body.appendChild(document.createElement("script")).innerHTML="(" + myScript + ")()"; | |||
</pre></code> | </pre></code> | ||
Revision as of 20:34, 22 February 2009
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.
Greasemonkey Manual |
Using Greasemonkey |
---|
Installing Scripts |
Monkey Menu |
Getting Help |
User Script Authoring |
Editing |
Environment |
API |
Description
This API object allows a User script to access "custom" properties--variable and functions defined in the page--set by the web page. 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.
unsafeWindow bypasses Greasemonkey's XPCNativeWrapper-based security model, which exists to make sure that malicious web pages cannot alter objects in such a way as to make greasemonkey 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 - especally if if they are executed for arbitrary web pages, such as those with @include *
, where the page authors may have subverted the environment in this way.
User script authors are strongly encouraged to learn how XPCNativeWrappers work, and how to perform the desired function within their security context, instead of using unsafeWindow to break out.
Examples | Alternatives to unsafeWindow | Notes
Syntax
unsafeWindow
- Value: Object
- Returns: Variant
- Compatibility: Greasemonkey 0.5b+
Examples
unsafeWindow.SomeVarInPage = "Testing";
unsafeWindow.SomeFunctionInPage("Test");
var oldFunction = unsafeWindow.SomeFunctionInPage;
unsafeWindow.SomeFunctionInPage = function(text) {
alert("Hijacked! Argument was " + text + ".");
return oldFunction(text);
};
- For issues with GM_getValue, GM_setValue and GM_xmlhttpRequest, see see 0.7.20080121.0_compatibility.
window.addEventListener("DOMTitleChanged", function(){
var redirectURL = window.name;
}, false);
var sGetter = document.createElement('script');
sGetter.type = "text/javascript";
sGetter.innerHTML = "function uXHR(url){"+
" var httpRequest = new XMLHttpRequest();"+
" httpRequest.onreadystatechange = function() { "+
" if(httpRequest.status == 301||httpRequest.status == 302){"+
" window.name=httpRequest.getResponseHeader('Location');"+
" document.title=document.title;"+
" }"+
" };"+
" httpRequest.open('HEAD', url, true);"+
" httpRequest.send(null);"+
"}";
document.body.appendChild(sGetter);
unsafeWindow.uXHR(url);
Alternatives to unsafeWindow
Events | Functions defined in the page | Attach script to page
Events
- Event listeners never need to be created on unsafeWindow. Rather than using
unsafeWindow.onclick = function(event) { ... };
use:
window.addEventListener("click", function(event) { /* some code */ }, false);
- See also 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
javascript:
URL, which is like using a bookmarklet. For example:
location.href = "javascript:void(pageFunc(123));";
- Larger blocks of code independent of the Greasemonkey context/APIs 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.
Attach script to page
Method 1
function myScript() {
for (var x in document) {
// do something with x
}
// blah blah blah
}
// attach script to page; script can therefore reference variables on the page, but likewise
// cannot use greasemonkey API methods
document.body.appendChild(document.createElement("script")).innerHTML="(" + myScript + ")()";
Method 2
This way is interesting for those who want:
- execute the init() function NOT in GM address space
- inject multiple css hacks
- inject multiple .js files
TODO: Confirm that @unwrap IS or IS NOT required for this to work (e.g. Should this example include the metadata block)
/*
Filename: hello-world.js
*/
(function()
{
inject_css();
var scripts = [
"http://mydomain.gov/misc/hello-injection.js",
"http://mydomain.gov/misc/hello-injection2.js"
];
/*
Be aware that the GM script, when executed on a webpage will fail to include this:
'file:///home/user/.mozilla/firefox/43obuw3o.default/gm_scripts/hello_world/lab-injection.js'
with the error: Error: init is not defined Sourcefile: javascript:void(init()); Line: 1
and you will get an security alert as well that elements from a remote site can't access local
files (which is good)
Be aware that the GM script, when executed on a webpage will fail to include this:
'/home/user/.mozilla/firefox/43obuw3o.default/gm_scripts/hello_world/lab-injection.js'
with the error: Error: init is not defined Sourcefile: javascript:void(init()); Line: 1
BE AWARE THAT THE PROTECTION FAULT ERROR WON'T BE SHOWN since no 'file://' is there.
this took me a lot of my time to figure out... ;P
- in this example we have two .js files, you can remove the second entry AND the , at the first one
if you only want one .js file
*/
for (i in scripts) {
var script = document.createElement("script");
script.src = scripts[i];
document.getElementsByTagName("head")[0].appendChild(script);
}
/* When the window is finished loading, attach the Shake-It on-click event. */
window.addEventListener(
"load"',
function(event) {
// Grab a reference to the Effect object which was loaded by the scriptaculous library earlier.
location.href = "javascript:void(init());";
},
"false"
);
}
)();
function addGlobalStyle(css) {
var head = document.getElementsByTagName("head")[0];
if (!head) {
return;
}
var style = document.createElement("style");
style.type = "text/css";
style.innerHTML = css;
head.appendChild(style);
}
function inject_css() {
document.title = document.title + " dynamically modified version";
addGlobalStyle(
".somedivclassname {" +
" margin: 0px 10px 0px 10px;" +
" margin-right: -12px;" +
" padding: 4px 0px 9px 0px;" +
"}"
);
}
/*
Filename: hello-injecting.js
*/
function init() {
alert('tut');
}