Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data


2017-04-01 19:10
2017-01-05 20:15


In general, Ember.js escapes or strips any user-supplied content
before inserting it in strings that will be sent to innerHTML.
However, the `tagName` property of an `Ember.View` was inserted into
such a string without being sanitized. This means that if an
application assigns a view's `tagName` to user-supplied data, a
specially-crafted payload could execute arbitrary JavaScript in the
context of the current domain ("XSS").

This vulnerability only affects applications that assign or bind
user-provided content to `tagName`.

Am I vulnerable?

The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.

Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.

Sign up for monitoring

Affected package information

Package Patched in Unaffected in
ember-source ~> 1.0.0.rc1.1,~> 1.0.0.rc2.1,~> 1.0.0.rc3.1,~> 1.0.0.rc4.1,~> 1.0.0.rc5.1,>= 1.0.0.rc6.1 None