2 lines
2.9 KiB
JSON
2 lines
2.9 KiB
JSON
{"affected":[{"affectedData":[{"product":"Secure File Transfer","vendor":"Biscom","versions":[{"status":"affected","version":"5.0.0000 through 5.1.1026"}]}],"source":"cve@rapid7.com"}],"configurations":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:a:biscom:secure_file_transfer:-:*:*:*:*:*:*:*","matchCriteriaId":"EFA39957-D9D2-41F6-BAC4-B6DCE183BC69","vulnerable":true}],"negate":false,"operator":"OR"}]}],"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's 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ón de expresión AngularJS en el campo Nombre para mostrar. Un usuario autenticado puede llenar este campo con una expresión AngularJS válida, envuelta en llaves dobles ({{}}). Esta expresión será 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ó en 5.1.1028."}],"id":"CVE-2017-5246","lastModified":"2026-06-17T01:20:14.383","metrics":{"cvssMetricV2":[{"acInsufInfo":true,"baseSeverity":"MEDIUM","cvssData":{"accessComplexity":"LOW","accessVector":"NETWORK","authentication":"SINGLE","availabilityImpact":"NONE","baseScore":4.0,"confidentialityImpact":"NONE","integrityImpact":"PARTIAL","vectorString":"AV:N/AC:L/Au:S/C:N/I:P/A:N","version":"2.0"},"exploitabilityScore":8.0,"impactScore":2.9,"obtainAllPrivilege":false,"obtainOtherPrivilege":false,"obtainUserPrivilege":false,"source":"nvd@nist.gov","type":"Primary","userInteractionRequired":false}],"cvssMetricV30":[{"cvssData":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":4.3,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"LOW","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"exploitabilityScore":2.8,"impactScore":1.4,"source":"nvd@nist.gov","type":"Primary"}]},"published":"2017-07-18T18:29:00.200","references":[{"source":"cve@rapid7.com","url":"https://cve.biscom.com/bis-sft-cv-0004/"},{"source":"cve@rapid7.com","tags":["Third Party Advisory"],"url":"https://twitter.com/i_bo0om/status/885050741567750145"},{"source":"af854a3a-2127-422b-91ae-364da2661108","url":"https://cve.biscom.com/bis-sft-cv-0004/"},{"source":"af854a3a-2127-422b-91ae-364da2661108","tags":["Third Party Advisory"],"url":"https://twitter.com/i_bo0om/status/885050741567750145"}],"sourceIdentifier":"cve@rapid7.com","vulnStatus":"Modified","weaknesses":[{"description":[{"lang":"en","value":"CWE-74"}],"source":"nvd@nist.gov","type":"Primary"}]}
|