-
Notifications
You must be signed in to change notification settings - Fork 4
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
Review ES6 impact #25
Comments
Well both Or did you ask the question in case one or both of those API were to be exposed to the sandbox? |
@Mickael-van-der-Beek That |
Finally started diving into this, although only a bit. So far the couple things that stood out as needing a closer look would be Also need to review what surfaces |
Also
still returns evel.Function as it should. |
What about |
@natevw Those are indeed leaked through the syntax as well. e.g:
and
Even though code execution is possible, it's not possible to pop an alert box due to the iframe not being attached to the DOM. To my knowledge, it's also not possible to escape the iframe itself. |
It also seems like Caja has had similar issues recently: http://blog.bentkowski.info/2017/11/yet-another-google-caja-bypasses-hat.html |
E.g. does the Reflect API (intro here: http://blog.keithcirkel.co.uk/metaprogramming-in-es6-part-2-reflect/) change anything?
new.target
? Anything else?The text was updated successfully, but these errors were encountered: