Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve security by limiting injection scope #1000

Closed
greasemonkey opened this issue Aug 8, 2009 · 3 comments
Closed

Improve security by limiting injection scope #1000

greasemonkey opened this issue Aug 8, 2009 · 3 comments

Comments

@greasemonkey
Copy link
Owner

See list posts:
http://groups.google.com/group/greasemonkey-users/msg/89adb81c9be5544a
http://groups.google.com/group/greasemonkey-users/msg/784f75d135ba410a

By allowing injection into file: URLs, arbitrary files whose paths are known can be stolen and transmitted to any server by malicious scripts. By allowing injection into about:cache, the location of the user profile can be discovered, making this flaw much more serious.

Do not allow scripts to run at file: or about: URLs. Since this has the very real potential (near guarantee) of causing backwards compatibility issues, a hidden default-off preference should be set up to override this, so that concerned users can override its value via about:config and restore the old behavior.

@arantius
Copy link
Collaborator

See also: http://greasemonkey.devjavu.com/ticket/110

Greasing the data: scheme can be useful.

@arantius
Copy link
Collaborator

Integrated into official tree.

@Martii
Copy link
Contributor

Martii commented Sep 17, 2009

Reference: commit.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants