# CVE-2020-27154: Code injection in n/a

> An attacker can execute arbitrary code in the Mitel BusinessCTI Client to view user information and application data due to improper input validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-86w2-3m2v-xrcg

## What is CVE-2020-27154?

CVE-2020-27154 is a high-severity code injection vulnerability in n/a, published on 18 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The chat window of Mitel BusinessCTI Enterprise (MBC-E) Client for Windows before 6.4.11 and 7.x before 7.0.3 could allow an attacker to gain access to user information by sending arbitrary code, due to improper input validation. A successful exploit could allow an attacker to view the user information and application data.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Mitel Businesscti Enterprise.

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

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

## Is CVE-2020-27154 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3176](https://insights.sbomify.com/CVE-2021-3176/): Information disclosure in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27154 is a high-severity code injection vulnerability in n/a, published on 18 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27154 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-27154/ (Markdown: https://insights.sbomify.com/CVE-2020-27154/index.md)
```

## Sources

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

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