Skip to content
This repository was archived by the owner on Nov 15, 2017. It is now read-only.

Address potential cross-scripting attempts #47

Closed
gorhill opened this issue Nov 11, 2013 · 3 comments
Closed

Address potential cross-scripting attempts #47

gorhill opened this issue Nov 11, 2013 · 3 comments

Comments

@gorhill
Copy link
Owner

gorhill commented Nov 11, 2013

As in http://labs.lachisterablanca.com/poc/bypass/index.php?%3Cscript%3Ealert(%27XSS%20WITH%20WHITESPACES%27);%3C/script%3E=anyValue

@insanitybit
Copy link

A naive/ simple approach to this should be simply storing the request and matching all scripting to the original requests. Right?

@gorhill
Copy link
Owner Author

gorhill commented Nov 11, 2013

This is what Chromium itself does. For an extension, I don't see how this is possible, as extensions can't block inline scripting (issue #35). I suppose the best option is to have webkit fix the code so this bypass doesn't work. I am trying to find out if there is a bug opened for this one particular case.

@gorhill
Copy link
Owner Author

gorhill commented Nov 18, 2013

Chromium is best position to do this, and they already have XSSAuditor, they should fix whatever holes it has at that level.

@gorhill gorhill closed this as completed Nov 18, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants