gsd-2013-4170
Vulnerability from gsd
Modified
2013-07-25 00:00
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`.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2013-4170",
"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\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": "GSD-2013-4170"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "ember-source",
"purl": "pkg:gem/ember-source"
}
}
],
"aliases": [
"CVE-2013-4170"
],
"details": "In general, Ember.js escapes or strips any user-supplied content\nbefore inserting it in strings that will be sent to innerHTML.\nHowever, the `tagName` property of an `Ember.View` was inserted into\nsuch a string without being sanitized. This means that if an\napplication assigns a view\u0027s `tagName` to user-supplied data, a\nspecially-crafted payload could execute arbitrary JavaScript in the\ncontext of the current domain (\"XSS\").\n\nThis vulnerability only affects applications that assign or bind\nuser-provided content to `tagName`.\n",
"id": "GSD-2013-4170",
"modified": "2013-07-25T00:00:00.000Z",
"published": "2013-07-25T00:00:00.000Z",
"references": [
{
"type": "WEB",
"url": "https://groups.google.com/forum/#!topic/ember-security/dokLVwwxAdM"
}
],
"schema_version": "1.4.0",
"summary": "Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data\n"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "secalert@redhat.com",
"ID": "CVE-2013-4170",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "ember-source",
"version": {
"version_data": [
{
"version_value": "ember-source \u003c 1.0.0.rc1.1"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "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`."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-79"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://rubysec.com/advisories/CVE-2013-4170/",
"refsource": "MISC",
"url": "https://rubysec.com/advisories/CVE-2013-4170/"
},
{
"name": "https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102",
"refsource": "MISC",
"url": "https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102"
},
{
"name": "https://groups.google.com/g/ember-security/c/dokLVwwxAdM",
"refsource": "MISC",
"url": "https://groups.google.com/g/ember-security/c/dokLVwwxAdM"
}
]
}
},
"github.com/rubysec/ruby-advisory-db": {
"cve": "2013-4170",
"date": "2013-07-25",
"description": "In general, Ember.js escapes or strips any user-supplied content\nbefore inserting it in strings that will be sent to innerHTML.\nHowever, the `tagName` property of an `Ember.View` was inserted into\nsuch a string without being sanitized. This means that if an\napplication assigns a view\u0027s `tagName` to user-supplied data, a\nspecially-crafted payload could execute arbitrary JavaScript in the\ncontext of the current domain (\"XSS\").\n\nThis vulnerability only affects applications that assign or bind\nuser-provided content to `tagName`.\n",
"gem": "ember-source",
"patched_versions": [
"~\u003e 1.0.0.rc1.1",
"~\u003e 1.0.0.rc2.1",
"~\u003e 1.0.0.rc3.1",
"~\u003e 1.0.0.rc4.1",
"~\u003e 1.0.0.rc5.1",
"\u003e= 1.0.0.rc6.1"
],
"title": "Ember.js Potential XSS Exploit When Binding `tagName` to User-Supplied Data\n",
"url": "https://groups.google.com/forum/#!topic/ember-security/dokLVwwxAdM"
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003c1.0.0.rc6.1",
"affected_versions": "All versions before 1.0.0.rc6.1",
"credit": "Yehuda Katz",
"cwe_ids": [
"CWE-1035",
"CWE-937"
],
"date": "2013-07-25",
"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\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`.",
"fixed_versions": [
"1.0.0.rc6.1"
],
"identifier": "CVE-2013-4170",
"identifiers": [
"CVE-2013-4170"
],
"not_impacted": "All versions starting from 1.0.0.rc6.1",
"package_slug": "gem/ember-source",
"pubdate": "2013-07-25",
"solution": "Upgrade to version 1.0.0.rc6.1 or above.",
"title": "Potential XSS Exploit When Binding tagName to User-Supplied Data",
"urls": [
"https://github.com/emberjs/ember.js/commit/f70a8fa0647ef3a13c3c8ea1d7ba7fca22ea5f8e",
"https://groups.google.com/forum/#!topic/ember-security/dokLVwwxAdM"
],
"uuid": "51dcaed3-1701-4ae4-9fdc-552492cd5d02"
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc4:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "1.0.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc1:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc2:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc3:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc5:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:emberjs:ember.js:1.0.0:rc6:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "secalert@redhat.com",
"ID": "CVE-2013-4170"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "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`."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-79"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102",
"refsource": "MISC",
"tags": [
"Patch",
"Third Party Advisory"
],
"url": "https://security.snyk.io/vuln/SNYK-RUBY-EMBERSOURCE-20102"
},
{
"name": "https://groups.google.com/g/ember-security/c/dokLVwwxAdM",
"refsource": "MISC",
"tags": [
"Mailing List",
"Patch",
"Third Party Advisory"
],
"url": "https://groups.google.com/g/ember-security/c/dokLVwwxAdM"
},
{
"name": "https://rubysec.com/advisories/CVE-2013-4170/",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://rubysec.com/advisories/CVE-2013-4170/"
}
]
}
},
"impact": {
"baseMetricV2": {
"acInsufInfo": false,
"cvssV2": {
"accessComplexity": "HIGH",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 2.6,
"confidentialityImpact": "NONE",
"integrityImpact": "PARTIAL",
"vectorString": "AV:N/AC:H/Au:N/C:N/I:P/A:N",
"version": "2.0"
},
"exploitabilityScore": 4.9,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "LOW",
"userInteractionRequired": true
},
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7
}
},
"lastModifiedDate": "2022-07-09T02:07Z",
"publishedDate": "2022-06-30T13:15Z"
}
}
}
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…