In general, Ember.js escapes or strips any user-supplied content before inserting it in strings that will be sent to innerHTML.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 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, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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`.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a ember-source
ember-source < 1.0.0.rc1.1
- ember-sourceRubyGems
fixed in 1.0.0.rc1.1
- ember-sourceRubyGems
From 1.0.0.rc2.0 · fixed in 1.0.0.rc2.1
- ember-sourceRubyGems
From 1.0.0.rc3.0 · fixed in 1.0.0.rc3.1
- ember-sourceRubyGems
From 1.0.0.rc4.0 · fixed in 1.0.0.rc4.1
- ember-sourceRubyGems
From 1.0.0.rc5.0 · fixed in 1.0.0.rc5.1
- ember-sourceRubyGems
From 1.0.0.rc6.0 · fixed in 1.0.0.rc6.1