Skip to content

Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data

Moderate severity GitHub Reviewed Published Jul 1, 2022 to the GitHub Advisory Database • Updated Aug 29, 2023

Package

bundler ember-source (RubyGems)

Affected versions

<= 1.0.0.rc1.0
= 1.0.0.rc2.0
= 1.0.0.rc3.0
= 1.0.0.rc4.0
= 1.0.0.rc5.0
= 1.0.0.rc6.0

Patched versions

1.0.0.rc1.1
1.0.0.rc2.1
1.0.0.rc3.1
1.0.0.rc4.1
1.0.0.rc5.1
1.0.0.rc6.1

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

Published by the National Vulnerability Database Jun 30, 2022
Published to the GitHub Advisory Database Jul 1, 2022
Reviewed Jul 12, 2022
Last updated Aug 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.071%
(32nd percentile)

Weaknesses

CVE ID

CVE-2013-4170

GHSA ID

GHSA-5m48-c37x-f792

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.