CVE-2013-4170: In general, Ember.js escapes or strips any user-supplied content before inserting it in strings that will be s

Q: How do I fix CVE-2013-4170?

ember.js: upgrade to 1.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2013-4170 being exploited?

CVE-2013-4170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-4170 affect?

CVE-2013-4170 affects ember.js. Severity is medium (CVSS 6.1). 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

Q: How urgent is CVE-2013-4170?

Priority 37/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2013-4170 is a medium-severity flaw (CVSS 6.1) affecting ember.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 on

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-06-30
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: emberjs

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-30 13:15 UTCPublished CVE record published
2026-06-16 23:56 UTCUpdated Record last modified

emberjs ember.js UPGRADE

Affected: < 1.0.0 · 1.0.0 rc1 · 1.0.0 rc2 · 1.0.0 rc3 · 1.0.0 rc4 · 1.0.0 rc5 · 1.0.0 rc6

Fixed in: 1.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ember.js || rpm -q ember.js || ember.js --version

2. UPGRADE to 1.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ember.js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ember.js

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4170?

ember.js: upgrade to 1.0.0. Exact commands for each OS are on this page.

Is CVE-2013-4170 being exploited?

CVE-2013-4170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4170 affect?

CVE-2013-4170 affects ember.js. Severity is medium (CVSS 6.1). 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

How urgent is CVE-2013-4170?

Priority 37/100. No elevated risk signals yet.

References

← Back to latest CVEs