CVE-2013-4170

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

Published: 2022-06-30 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2013-4170 is rated Moderate Risk (43.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2013-4170

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-07-11 0.36% 0.32% -0.05%
2 2025-07-06 0.05% 0.36% +0.31%
3 2023-03-07 — 0.05% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2013-4170

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]
2.6 2.0 LOW
AV:N/AC:H/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 4.9 2.9 [email protected]

Weakness enumeration for CVE-2013-4170

GitHub Security Advisory for CVE-2013-4170

GHSA-5m48-c37x-f792 · Severity: medium · Ecosystem: rubygems — Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data

OS Trackers for CVE-2013-4170

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2013-4170

Affected software / configurations for CVE-2013-4170

Vendor Product Version Raw CPE
emberjs ember.js < 1.0.0 cpe:2.3:a:emberjs:ember.js:*:*:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc1:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc2:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc3:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc4:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc5:*:*:*:*:*:*
emberjs ember.js 1.0.0 cpe:2.3:a:emberjs:ember.js:1.0.0:rc6:*:*:*:*:*:*

References for CVE-2013-4170

cvelogic Threat Intelligence