Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2022-41223

MiVoice Connect

Mitel / MiVoice Connect

Watch CVE-2022-41223 Browse KEV feed
Severity
CVSS 6.8 · Medium
Confidence
Confirmed
Exploit status
Exploited in the wild
EPSS
10.7%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-41223 is a vulnerability affecting Mitel MiVoice Connect. The Director database component of MiVoice Connect through 19.3 (22.22.6100.0) could allow an authenticated attacker to conduct a code-injection...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV.

Who is affected?

Mitel / MiVoice Connect.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

MiVoice Connect

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.

Published
22 Nov 2022
Exploitation Reported
21 Feb 2023
Attack vector
Adjacent
Complexity
Low
Privileges
High
User interaction
None

Tags

malware ransomware cisa

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 21 Feb 2023

A trusted third party reported exploitation.

Used in malware

CISA

Recorded 21 Feb 2023

Malware families have been linked to exploitation of this CVE.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2023-02-21 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

6.8 Medium

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS

10.7%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Improper Control of Generation of Code ('Code Injection') CWE-94

Timeline

From disclosure to observed exploitation

  1. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  2. 00:00 UTC

    First public exploitation report

    Exploit observed in malware

  3. 00:00 UTC

    CVE published

    Vulnerability disclosed publicly

  4. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-41223

Sample API response 
{
  "cve_id": "CVE-2022-41223",
  "confidence": "Confirmed",
  "cvss_score": 6.8,
  "cvss_estimated": false,
  "epss_score": 0.10657,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}