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`.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Link | Tags |
---|---|
https://rubysec.com/advisories/CVE-2013-4170/ | third party advisory |
https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102 | third party advisory patch |
https://groups.google.com/g/ember-security/c/dokLVwwxAdM | mailing list third party advisory patch |