Description
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`.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | ember-source | ember-source < 1.0.0.rc1.1 |
References
- https://groups.google.com/g/ember-security/c/dokLVwwxAdMMailing List, Patch, Third Party Advisory
- https://rubysec.com/advisories/CVE-2013-4170/Third Party Advisory
- https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102Patch, Third Party Advisory
- https://groups.google.com/g/ember-security/c/dokLVwwxAdMMailing List, Patch, Third Party Advisory
- https://rubysec.com/advisories/CVE-2013-4170/Third Party Advisory
- https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102Patch, Third Party Advisory
Timeline
- Published
- Jun 30, 2022
- Last modified
- Jun 16, 2026
- NVD status
- Modified