# CVE-2020-27646: Information disclosure in n/a

> Attackers can steal user credentials from Biscom Secure File Transfer, potentially leading to unauthorized access and data exposure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pgcj-52hg-vjr8

## What is CVE-2020-27646?

CVE-2020-27646 is a medium-severity vulnerability in n/a, published on 22 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Biscom Secure File Transfer (SFT) before 5.1.1082 and 6.x before 6.0.1011 allows user credential theft.

## Which versions are affected by CVE-2020-27646?

It affects 1 product.


Products: Biscom Secure File Transfer.

## How do I fix CVE-2020-27646?

No fix has been published for CVE-2020-27646 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-27646 being exploited?

There is no known exploitation of CVE-2020-27646 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-8796](https://insights.sbomify.com/CVE-2020-8796/): Code injection in n/a (critical 9.8)
- [CVE-2016-10710](https://insights.sbomify.com/CVE-2016-10710/): Missing authorization in n/a (high 8.1)
- [CVE-2020-8503](https://insights.sbomify.com/CVE-2020-8503/): Missing authorization in n/a (medium 6.5)
- [CVE-2017-5247](https://insights.sbomify.com/CVE-2017-5247/): Cross-site scripting in Secure File Transfer (medium 5.4)
- [CVE-2017-5241](https://insights.sbomify.com/CVE-2017-5241/): Cross-site scripting in Secure File Transfer (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27646 and fix it if it is affected.

What it is: CVE-2020-27646 is a medium-severity vulnerability in n/a, published on 22 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-27646 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-27646/ (Markdown: https://insights.sbomify.com/CVE-2020-27646/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-27646
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-27646
- OSV: https://osv.dev/vulnerability/CVE-2020-27646

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-27646/
Summaries are generated and may contain mistakes; the official description above is the record.