CVE-2013-4170: Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data

CVE-2013-4170 · Severity: low · CVSS 3.1 · Published 2022-07-01

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

Technologies: ember-source (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2013-4170 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-4170 being exploited in the wild.
How severe is CVE-2013-4170?
Low severity, with a CVSS score of 3.1, published 1 July 2022.
Which products and versions are affected?
ember-source (RubyGems) ECOSYSTEM:introduced=0,fixed=1.0.0.rc1.1.
Is there a fix for CVE-2013-4170?
Yes. ember-source (RubyGems): upgrade to 1.0.0.rc1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-4170?
Check whether you run ember-source (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ember-source (RubyGems): upgrade to 1.0.0.rc1.1 or later
    bundle update ember-source

Affected products

  • ember-source (RubyGems) ECOSYSTEM:introduced=0,fixed=1.0.0.rc1.1

Identifiers

  • CVE-2013-4170
  • GHSA-5m48-c37x-f792

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.