In general, Ember.js escapes or strips any user-supplied content before inserting it in strings that will be sent to innerHTML. However, we have identified a vulnerability that could lead to unescaped content being inserted into the innerHTML string without being sanitized.

When using the {{group}} helper, user supplied content in the template was not being sanitized. Though the vulnerability exists in Ember.js proper, it is only exposed via the use of an experimental plugin.

In applications that use the {{group}} helper, a specially-crafted payload could execute arbitrary JavaScript in the context of the current domain ("XSS").

This vulnerability only affects applications that use the {{group}} helper to display user-provided content.

In general, Ember.js escapes or strips any user-supplied content before inserting it in strings that will be sent to innerHTML. However, we have identified a vulnerability that could lead to unescaped content being inserted into the innerHTML string without being sanitized.

When a primitive value is used as the Handlebars context, that value is not properly escaped. An example of this would be using the {{each}} helper to iterate over an array of user-supplied strings and using {{this}} inside the block to display each string.

In applications that contain templates whose context is a primitive value and use the {{this}} keyword to display that value, a specially-crafted payload could execute arbitrary JavaScript in the context of the current domain ("XSS").

This vulnerability affects applications that contain templates whose context is set to a user-supplied primitive value (such as a string or number) and also contain the {{this}} special Handlebars variable to display the value.

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.