Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data
GHSA-5m48-c37x-f792 · CVE-2013-4170
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2013-4170
- PACKAGE https://github.com/emberjs/ember.js
- WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/ember-source/CVE-2013-4170.yml
- WEB https://groups.google.com/forum/#!topic/ember-security/dokLVwwxAdM
- WEB https://groups.google.com/g/ember-security/c/dokLVwwxAdM
- WEB https://rubysec.com/advisories/CVE-2013-4170
- WEB https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102
Ready to move
Start Securing
Free, no credit card | First findings in minutes