Advisory

GHSA-5m48-c37x-f792

Also known as: CVE-2013-4170

Summary

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

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-07-01 00:01 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

ember-source

RubyGems · All systems

Affected

  • introduced 0, fixed 1.0.0.rc1.1 (ecosystem)

Fixed versions

1.0.0.rc1.1

Fix

The export has no generic command for this ecosystem.

ember-source

RubyGems · All systems

Affected

  • introduced 1.0.0.rc2.0, fixed 1.0.0.rc2.1 (ecosystem)

Fixed versions

1.0.0.rc2.1

Fix

The export has no generic command for this ecosystem.

ember-source

RubyGems · All systems

Affected

  • introduced 1.0.0.rc3.0, fixed 1.0.0.rc3.1 (ecosystem)

Fixed versions

1.0.0.rc3.1

Fix

The export has no generic command for this ecosystem.

ember-source

RubyGems · All systems

Affected

  • introduced 1.0.0.rc4.0, fixed 1.0.0.rc4.1 (ecosystem)

Fixed versions

1.0.0.rc4.1

Fix

The export has no generic command for this ecosystem.

ember-source

RubyGems · All systems

Affected

  • introduced 1.0.0.rc5.0, fixed 1.0.0.rc5.1 (ecosystem)

Fixed versions

1.0.0.rc5.1

Fix

The export has no generic command for this ecosystem.

ember-source

RubyGems · All systems

Affected

  • introduced 1.0.0.rc6.0, fixed 1.0.0.rc6.1 (ecosystem)

Fixed versions

1.0.0.rc6.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences