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

> Weak encryption in the client allows attackers to steal user credentials and gain unauthorized system access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fxr3-63w8-hvhx

## What is CVE-2020-10377?

CVE-2020-10377 is a critical vulnerability in n/a, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weak encryption vulnerability in Mitel MiVoice Connect Client before 214.100.1214.0 could allow an unauthenticated attacker to gain access to user credentials. A successful exploit could allow an attacker to access the system with compromised user credentials.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Mitel Mivoice Connect Client.

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

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

## Is CVE-2020-10377 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12456](https://insights.sbomify.com/CVE-2020-12456/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10377 is a critical vulnerability in n/a, published on 17 Apr 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-10377 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-10377/ (Markdown: https://insights.sbomify.com/CVE-2020-10377/index.md)
```

## Sources

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

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