CVE-2020-8503

Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003 allows Insecure Direct Object Reference (IDOR) by an authenticated sender because of an error in a file-upload feature. This is fixed in 5.1.1068 and 6.0.1004.

CVSS v3 6.5 MEDIUM
CVSS v2.0 3.5 LOW

6.5^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.8 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

3.5^/10

CVSS v2.0 : LOW

Vector : AV:N/AC:M/Au:S/C:P/I:N/A:N

Exploitability : 6.8 / Impact : 2.9

Access Vector NETWORK

Access Complexity MEDIUM

Authentication SINGLE

Confidentiality Impact PARTIAL

Integrity Impact NONE

Availability Impact NONE

References

Link	Resource
https://cve.biscom.com/bis-sft-cv-0008	Vendor Advisory

Configurations

Configuration 1 (hide)

OR	cpe:2.3:a:biscom:secure_file_transfer::::::::
	cpe:2.3:a:biscom:secure_file_transfer::::::::

History

No history.

Information

Published : 2020-01-31 20:15

Updated : 2023-12-10 13:13

NVD link : CVE-2020-8503

Mitre link : CVE-2020-8503

CVE.ORG link : CVE-2020-8503

JSON object : View

Products Affected

biscom

secure_file_transfer

CWE

CWE-639

Authorization Bypass Through User-Controlled Key

{"id": "CVE-2020-8503", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 3.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:S/C:P/I:N/A:N", "authentication": "SINGLE", "integrityImpact": "NONE", "accessComplexity": "MEDIUM", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "LOW", "obtainAllPrivilege": false, "exploitabilityScore": 6.8, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2020-01-31T20:15:11.243", "references": [{"url": "https://cve.biscom.com/bis-sft-cv-0008", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003 allows Insecure Direct Object Reference (IDOR) by an authenticated sender because of an error in a file-upload feature. This is fixed in 5.1.1068 and 6.0.1004."}, {"lang": "es", "value": "Biscom Secure File Transfer (SFT) versiones 5.0.1050 hasta 5.1.1067 y 6.0.1000 hasta 6.0.1003, permite una Referencia Directa a Objetos No Segura (IDOR) por parte de un remitente autenticado debido a un error en una funcionalidad de carga de archivos. Esto se corrigi\u00f3 en las versiones 5.1.1068 y 6.0.1004."}], "lastModified": "2020-02-05T16:32:56.740", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:biscom:secure_file_transfer:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "07E022ED-DE65-4972-B624-CC0ADC55B219", "versionEndIncluding": "5.1.1067", "versionStartIncluding": "5.0.1050"}, {"criteria": "cpe:2.3:a:biscom:secure_file_transfer:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C637C8E4-2963-4D36-914F-9F929959D12B", "versionEndIncluding": "6.0.1003", "versionStartIncluding": "6.0.1000"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}