# CVE-2020-27688: Weak cryptography in n/a

> RVTools uses static encryption keys for stored passwords, allowing attackers to decrypt vSphere credentials from configuration files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m63f-6r3q-6w4p

## What is CVE-2020-27688?

CVE-2020-27688 is a high-severity vulnerability in n/a, published on 5 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RVToolsPasswordEncryption.exe in RVTools 4.0.6 allows users to encrypt passwords to be used in the configuration files. This encryption used a static IV and key, and thus using the Decrypt() method from VISKD.cs from the RVTools.exe executable allows for decrypting the encrypted passwords. The accounts used in the configuration files have access to vSphere instances.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Robware Rvtools.

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

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

## Is CVE-2020-27688 being exploited?

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

Public exploit code:

- CVE-2020-27688 (github_poc): https://github.com/matthiasmaes/CVE-2020-27688

## Other vulnerabilities in n/a

- [CVE-2023-44303](https://insights.sbomify.com/CVE-2023-44303/): Weak cryptography in RVTools (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27688 is a high-severity vulnerability in n/a, published on 5 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27688 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-27688/ (Markdown: https://insights.sbomify.com/CVE-2020-27688/index.md)
```

## Sources

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

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