CVE-2013-4170 — ember-source
MEDIUMCVE-2013-4170 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in ember-source. A fix is available for ember-source — see the affected versions and patch details below.
Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2013-4170 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
ember-source💎ember-source💎ember-source💎ember-source💎ember-source💎ember-sourceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | ember-source | all versions | 1.0.0.rc1.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.0.0.rc2.0&&< 1.0.0.rc2.1 | 1.0.0.rc2.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.0.0.rc3.0&&< 1.0.0.rc3.1 | 1.0.0.rc3.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.0.0.rc4.0&&< 1.0.0.rc4.1 | 1.0.0.rc4.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.0.0.rc5.0&&< 1.0.0.rc5.1 | 1.0.0.rc5.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.0.0.rc6.0&&< 1.0.0.rc6.1 | 1.0.0.rc6.1bundle update ember-source --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ember-source, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ember-source to 1.0.0.rc1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4170 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4170 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2013-4170. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2013-4170 in your dependencies?
O3 Security finds CVE-2013-4170 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.