CVE-2013-4170

MEDIUM
6.1
CVSS Score
Published: June 30, 2022 at 12:38 PM UTC
Updated: June 16, 2026 at 11:56 PM UTC
1 product affected across 1 vendorEmberjs

Using ember-source by N/A?

Get instant alerts when new vulnerabilities affect ember-source - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.1
Exploit prediction
EPSS 0.9%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 1.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.0.0.rc1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_MISCMailing ListPatchThird Party Advisory
https://groups.google.com/g/ember-security/c/dokLVwwxAdM
x_refsource_MISCThird Party Advisory
https://rubysec.com/advisories/CVE-2013-4170/

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-79

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card