# CVE-2022-41223: Mitel MiVoice Connect Code Injection

> An authenticated attacker can execute arbitrary code in the MiVoice Connect Director database by injecting crafted data due to insufficient type restrictions.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 21 Feb 2023 (CISA KEV), used in ransomware
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-7vhc-x99q-vfpj

## What is CVE-2022-41223?

CVE-2022-41223 is a medium-severity code injection vulnerability in n/a, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Director database component of MiVoice Connect through 19.3 (22.22.6100.0) could allow an authenticated attacker to conduct a code-injection attack via crafted data due to insufficient restrictions on the database data type.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-41223?

It affects 1 product.


Products: Mitel Mivoice Connect.

## How do I fix CVE-2022-41223?

No fix has been published for CVE-2022-41223 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Mar 2023.

## Is CVE-2022-41223 being exploited?

Yes. Attackers have exploited CVE-2022-41223 in the wild since at least 21 Feb 2023, including in ransomware campaigns.

## Other vulnerabilities in n/a

- [CVE-2022-29499](https://insights.sbomify.com/CVE-2022-29499/): Mitel MiVoice Connect Data Validation (critical 9.8, exploited in the wild)
- [CVE-2022-40765](https://insights.sbomify.com/CVE-2022-40765/): Mitel MiVoice Connect Command Injection (medium 6.8, exploited in the wild)
- [CVE-2023-32748](https://insights.sbomify.com/CVE-2023-32748/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-31457](https://insights.sbomify.com/CVE-2023-31457/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-31458](https://insights.sbomify.com/CVE-2023-31458/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41223 and fix it if it is affected.

What it is: CVE-2022-41223 is a medium-severity code injection vulnerability in n/a, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-41223 in the wild since at least 21 Feb 2023, including in ransomware campaigns.

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-2022-41223/ (Markdown: https://insights.sbomify.com/CVE-2022-41223/index.md)
```

## Sources

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

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