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

XSS Vulnerability #375

Closed
ghost opened this issue Dec 16, 2013 · 2 comments
Closed

XSS Vulnerability #375

ghost opened this issue Dec 16, 2013 · 2 comments

Comments

@ghost
Copy link

ghost commented Dec 16, 2013

Hi there.

I am not sure if this has been patched already, but here's a vulnerability that can make Polymer execute arbitrary code. Please don't allow this in Polymer, as it opens up security holes.

...

Whitepaper: http://ruxcon.org.au/assets/slides/CSP-kuza55.pptx

@sjmiles
Copy link
Contributor

sjmiles commented Dec 16, 2013

It's not clear how it's possible to inject into <element> like that as an XSS attack. There is no input that feeds that tag. If the attacker controls that HTML, they can simply include their script directly, Polymer is not relevant. Can you help me understand how this is an exploit?

Fwiw, it's not possible to 'remove all eval' from Polymer. However, to ensure a Polymer application is CSP compliant, one can run it through the vulcanize tool.

Thank you for the report, please let us know if you find other problematic scenarios.

@sorvell
Copy link
Contributor

sorvell commented Aug 11, 2014

Closed due to age, please re-open if this is still an issue.

@sorvell sorvell closed this as completed Aug 11, 2014
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

2 participants