CVE-2013-4170
Summary
| CVE | CVE-2013-4170 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-06-30 13:15:00 UTC |
| Updated | 2022-07-09 02:07:00 UTC |
| 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`. |
Risk And Classification
Problem Types: CWE-79
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Emberjs | Ember.js | All | All | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc1 | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc2 | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc3 | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc4 | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc5 | All | All |
| Application | Emberjs | Ember.js | 1.0.0 | rc6 | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| CVE-2013-4170 (ember-source): Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data - RubySec | MISC | rubysec.com | |
| [CVE-2013-4170] Potential XSS Exploit When Binding `tagName` to User-Supplied Data | MISC | groups.google.com | |
| Cross-site Scripting (XSS) in ember-source | CVE-2013-4170 | Snyk | MISC | security.snyk.io | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.