ghsa-5m48-c37x-f792
Vulnerability from github
Published
2022-07-01 00:01
Modified
2023-01-26 22:40
Severity ?
VLAI Severity ?
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.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.0.0.rc1.0"
},
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.0.rc1.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0.rc2.0"
},
{
"fixed": "1.0.0.rc2.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0.rc2.0"
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0.rc3.0"
},
{
"fixed": "1.0.0.rc3.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0.rc3.0"
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0.rc4.0"
},
{
"fixed": "1.0.0.rc4.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0.rc4.0"
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0.rc5.0"
},
{
"fixed": "1.0.0.rc5.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0.rc5.0"
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0.rc6.0"
},
{
"fixed": "1.0.0.rc6.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0.rc6.0"
]
}
],
"aliases": [
"CVE-2013-4170"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2022-07-12T21:27:47Z",
"nvd_published_at": "2022-06-30T13:15:00Z",
"severity": "MODERATE"
},
"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\u0027s `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`.",
"id": "GHSA-5m48-c37x-f792",
"modified": "2023-01-26T22:40:32Z",
"published": "2022-07-01T00:01:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-4170"
},
{
"type": "PACKAGE",
"url": "https://github.com/emberjs/ember.js"
},
{
"type": "WEB",
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/ember-source/CVE-2013-4170.yml"
},
{
"type": "WEB",
"url": "https://groups.google.com/forum/#!topic/ember-security/dokLVwwxAdM"
},
{
"type": "WEB",
"url": "https://groups.google.com/g/ember-security/c/dokLVwwxAdM"
},
{
"type": "WEB",
"url": "https://rubysec.com/advisories/CVE-2013-4170"
},
{
"type": "WEB",
"url": "https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…