CVE-2013-4170

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`.

Category

6.1
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.10%
Third-Party Advisory google.com Third-Party Advisory rubysec.com Third-Party Advisory snyk.io
Affected: n/a ember-source
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2013-4170?
CVE-2013-4170 has been scored as a medium severity vulnerability.
How to fix CVE-2013-4170?
To fix CVE-2013-4170, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2013-4170 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2013-4170 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2013-4170?
CVE-2013-4170 affects n/a ember-source.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.