CVE-2013-4170
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").
Does this matter?
Lower severity and a low EPSS score (0.89%). Track it; it rarely justifies an emergency change on its own.
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`.
- CVSS 3.1
- 6.1 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- 0.89% probability · 57th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-79
- Affected
- emberjs/ember.js
- Source
- secalert@redhat.com
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.