CVE-2017-5246 (GCVE-0-2017-5246)
Vulnerability from cvelistv5 – Published: 2017-07-18 18:00 – Updated: 2024-08-05 14:55
VLAI?
Summary
Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker's display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028.
Severity ?
No CVSS data available.
CWE
- Cross-Site Scripting
Assigner
References
| URL | Tags | |||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Biscom | Secure File Transfer |
Affected:
5.0.0000 through 5.1.1026
|
Date Public ?
2017-07-18 00:00
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-05T14:55:35.789Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://twitter.com/i_bo0om/status/885050741567750145"
},
{
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://cve.biscom.com/bis-sft-cv-0004/"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "Secure File Transfer",
"vendor": "Biscom",
"versions": [
{
"status": "affected",
"version": "5.0.0000 through 5.1.1026"
}
]
}
],
"datePublic": "2017-07-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker\u0027s display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028."
}
],
"problemTypes": [
{
"descriptions": [
{
"description": "Cross-Site Scripting",
"lang": "en",
"type": "text"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2020-02-20T21:06:21.000Z",
"orgId": "9974b330-7714-4307-a722-5648477acda7",
"shortName": "rapid7"
},
"references": [
{
"tags": [
"x_refsource_MISC"
],
"url": "https://twitter.com/i_bo0om/status/885050741567750145"
},
{
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://cve.biscom.com/bis-sft-cv-0004/"
}
],
"x_legacyV4Record": {
"CVE_data_meta": {
"ASSIGNER": "cve@rapid7.com",
"ID": "CVE-2017-5246",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "Secure File Transfer",
"version": {
"version_data": [
{
"version_value": "5.0.0000 through 5.1.1026"
}
]
}
}
]
},
"vendor_name": "Biscom"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker\u0027s display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "Cross-Site Scripting"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://twitter.com/i_bo0om/status/885050741567750145",
"refsource": "MISC",
"url": "https://twitter.com/i_bo0om/status/885050741567750145"
},
{
"name": "https://cve.biscom.com/bis-sft-cv-0004/",
"refsource": "CONFIRM",
"url": "https://cve.biscom.com/bis-sft-cv-0004/"
}
]
}
}
}
},
"cveMetadata": {
"assignerOrgId": "9974b330-7714-4307-a722-5648477acda7",
"assignerShortName": "rapid7",
"cveId": "CVE-2017-5246",
"datePublished": "2017-07-18T18:00:00.000Z",
"dateReserved": "2017-01-09T00:00:00.000Z",
"dateUpdated": "2024-08-05T14:55:35.789Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2017-5246",
"date": "2026-04-25",
"epss": "0.0028",
"percentile": "0.51345"
},
"fkie_nvd": {
"configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:biscom:secure_file_transfer:-:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"EFA39957-D9D2-41F6-BAC4-B6DCE183BC69\"}]}]}]",
"descriptions": "[{\"lang\": \"en\", \"value\": \"Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker\u0027s display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028.\"}, {\"lang\": \"es\", \"value\": \"Biscom Secure File Transfer es vulnerable a la inyecci\\u00f3n de expresi\\u00f3n AngularJS en el campo Nombre para mostrar. Un usuario autenticado puede llenar este campo con una expresi\\u00f3n AngularJS v\\u00e1lida, envuelta en llaves dobles ({{}}). Esta expresi\\u00f3n ser\\u00e1 evaluada por cualquier otro usuario autenticado que vea el nombre para mostrar del atacante. Las versiones afectadas son 5.0.0000 a 5.1.1026. El problema se solucion\\u00f3 en 5.1.1028.\"}]",
"id": "CVE-2017-5246",
"lastModified": "2024-11-21T03:27:21.703",
"metrics": "{\"cvssMetricV30\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.0\", \"vectorString\": \"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\", \"baseScore\": 4.3, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"LOW\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 1.4}], \"cvssMetricV2\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"2.0\", \"vectorString\": \"AV:N/AC:L/Au:S/C:N/I:P/A:N\", \"baseScore\": 4.0, \"accessVector\": \"NETWORK\", \"accessComplexity\": \"LOW\", \"authentication\": \"SINGLE\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"PARTIAL\", \"availabilityImpact\": \"NONE\"}, \"baseSeverity\": \"MEDIUM\", \"exploitabilityScore\": 8.0, \"impactScore\": 2.9, \"acInsufInfo\": true, \"obtainAllPrivilege\": false, \"obtainUserPrivilege\": false, \"obtainOtherPrivilege\": false, \"userInteractionRequired\": false}]}",
"published": "2017-07-18T18:29:00.200",
"references": "[{\"url\": \"https://cve.biscom.com/bis-sft-cv-0004/\", \"source\": \"cve@rapid7.com\"}, {\"url\": \"https://twitter.com/i_bo0om/status/885050741567750145\", \"source\": \"cve@rapid7.com\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://cve.biscom.com/bis-sft-cv-0004/\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://twitter.com/i_bo0om/status/885050741567750145\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Third Party Advisory\"]}]",
"sourceIdentifier": "cve@rapid7.com",
"vulnStatus": "Modified",
"weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-74\"}]}]"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2017-5246\",\"sourceIdentifier\":\"cve@rapid7.com\",\"published\":\"2017-07-18T18:29:00.200\",\"lastModified\":\"2025-04-20T01:37:25.860\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Biscom Secure File Transfer is vulnerable to AngularJS expression injection in the Display Name field. An authenticated user can populate this field with a valid AngularJS expression, wrapped in double curly-braces ({{ }}). This expression will be evaluated by any other authenticated user who views the attacker\u0027s display name. Affected versions are 5.0.0000 through 5.1.1026. The Issue is fixed in 5.1.1028.\"},{\"lang\":\"es\",\"value\":\"Biscom Secure File Transfer es vulnerable a la inyecci\u00f3n de expresi\u00f3n AngularJS en el campo Nombre para mostrar. Un usuario autenticado puede llenar este campo con una expresi\u00f3n AngularJS v\u00e1lida, envuelta en llaves dobles ({{}}). Esta expresi\u00f3n ser\u00e1 evaluada por cualquier otro usuario autenticado que vea el nombre para mostrar del atacante. Las versiones afectadas son 5.0.0000 a 5.1.1026. El problema se solucion\u00f3 en 5.1.1028.\"}],\"metrics\":{\"cvssMetricV30\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.0\",\"vectorString\":\"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\",\"baseScore\":4.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":1.4}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:S/C:N/I:P/A:N\",\"baseScore\":4.0,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"SINGLE\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":8.0,\"impactScore\":2.9,\"acInsufInfo\":true,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-74\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:biscom:secure_file_transfer:-:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"EFA39957-D9D2-41F6-BAC4-B6DCE183BC69\"}]}]}],\"references\":[{\"url\":\"https://cve.biscom.com/bis-sft-cv-0004/\",\"source\":\"cve@rapid7.com\"},{\"url\":\"https://twitter.com/i_bo0om/status/885050741567750145\",\"source\":\"cve@rapid7.com\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://cve.biscom.com/bis-sft-cv-0004/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://twitter.com/i_bo0om/status/885050741567750145\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…