CriticalCVE-2022-40765

    Mitel MiVoice Connect Command Injection Vulnerability (CVE-2022-40765)

    Published In CISA KEV since Sources: pwn.watch, CVE.org

    What is affected, what to do

    A vulnerability in the Edge Gateway component of Mitel MiVoice Connect through 19.3 (22.22.6100.0) could allow an authenticated attacker with internal network access to conduct a command-injection attack, due to insufficient restriction of URL parameters.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Mitel MiVoice Connect lte *..22.22.6100.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.8

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    10.6 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 95.8

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    234.12 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    10.6 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    95.8
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 January 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-77

    Response and mitigation

    Why act now?

    Prioritisation rationale

    On paper this is a moderate bug — it requires adjacent-network access and high-privilege credentials — but the CISA ransomware-use flag and the very high exploitation likelihood show that attackers use it in practice, typically after gaining an initial foothold or harvesting admin credentials. VoIP edge appliances like the Edge Gateway make ideal beachheads: Linux-based, rarely covered by EDR, often bridging DMZ and internal networks, and patched on slow cycles. If your Edge Gateway admin interface is reachable from user, VPN or DMZ networks, treat this as high priority and patch within days; if management is strictly confined to an MFA-protected admin network, a prompt but regular patch cycle is defensible.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Identify every Mitel MiVoice Connect deployment running the Edge Gateway component and confirm its version. MiVoice Connect through 19.3 (22.22.6100.0) is affected. Prioritise Edge Gateway appliances sitting in DMZ or teleworker segments.
      • Patch: Upgrade to a release later than 19.3 (22.22.6100.0). Patch available from the vendor — check the Mitel security advisory for the exact fixed version. Do not defer exposed Edge Gateways to the next routine window.
      • Lock down admin access: Restrict the Edge Gateway web administration interface via ACL/firewall so it is reachable only from a dedicated admin or jump-host network. Immediately block access from user VLANs, VPN pools and guest Wi-Fi.
      • Rotate credentials: Exploitation requires high-privilege authentication, so reset all administrative accounts on the Edge Gateway and the MiVoice Connect Director management plane. Remove shared or default passwords and disable unused accounts.
      • Compromise assessment: Before and after patching, review web access logs, running processes, cron jobs and /tmp and web directories on the appliance for signs of command execution. If anything turns up: isolate the appliance, capture a forensic image, and rebuild rather than clean.
      • Reporting obligations: If exploitation is confirmed, trigger internal IR escalation and the NIS2 early-warning clock (24 h).

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the Edge Gateway in its own zone. Inbound, permit only the services teleworker/SBC functions strictly require; management interfaces from the admin network only. Apply default-deny egress, allowing only known Mitel destinations, NTP and DNS — this kills reverse shells and tool staging.
      • WAF/IPS: In front of the admin interface, enable rules for shell metacharacters in URL parameters, e.g. Suricata content matches on %3B, %7C, %60, %24%28, $(, ;, | in http.uri/query string towards Edge Gateway IPs. Turn on generic command-injection signatures (ET WEB_SERVER, OWASP CRS 932xxx group) in blocking mode for these hosts.
      • IAM/least privilege: Limit Edge Gateway admin rights to a small set of named individuals. Where possible, force admin access through a PAM/jump host with MFA and session recording.
      • Lateral-movement barrier: Block connections from the Edge Gateway into the internal network (SMB, RDP, LDAP, WinRM, SSH) unless demonstrably required for telephony. The appliance is a classic foothold with no EDR coverage.
      • Centralised logging: Forward syslog, web server and authentication logs from the appliance to the SIEM so attackers cannot destroy evidence by wiping local logs.

    3. Runbook step 3

      Detection rules

      • Edge Gateway web access log: Requests to admin endpoints carrying shell metacharacters or command fragments in parameters. SPL sketch: index=mitel sourcetype=access_combined (uri_query="*%3B*" OR uri_query="*%7C*" OR uri_query="*%60*" OR uri_query="*%24%28*" OR uri_query="*wget*" OR uri_query="*curl*")
      • Process ancestry (auditd/EDR, if an agent or log export is possible): Web server or interpreter process (httpd, php, apache) spawning sh, bash, curl, wget, nc, python, perl. auditd rule: -a always,exit -F arch=b64 -S execve -F euid=<webserver-uid> -k mitel_cmdi, then filter in the SIEM on exe matching shells or downloaders.
      • Network telemetry (Zeek/Suricata/firewall): New or rare outbound connections from Edge Gateway IPs to the internet, especially to non-Mitel destinations, high ports, or long-lived sessions (reverse shell, tunnelling). KQL sketch: CommonSecurityLog | where SourceIP in (mitel_edge_ips) and DestinationIP !in (allowlist) | summarize count() by DestinationIP, DestinationPort
      • Authentication anomalies: Admin logins to the Edge Gateway from source IPs outside the admin network, at odd hours, or following bursts of failed attempts — the prerequisite for exploitation.
      • Filesystem artefacts: New executables or scripts in /tmp, /var/tmp or the web root; modified crontabs; new SSH keys in authorized_keys.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A vulnerability in the Edge Gateway component of Mitel MiVoice Connect through 19.3 (22.22.6100.0) could allow an authenticated attacker with internal network access to conduct a command-injection attack, due to insufficient restriction of URL parameters.

    Source: pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    mitelmivoice_connect
    • ≤ 22.22.6100.0
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection')

      Class

      The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

      Entry at MITRE CWE-77

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • mitel.comsupport/security-advisoriesVendor advisory
    • mitel.comVendor advisory: Mitel MiVoice ConnectMitigation, Vendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2022-40765government-resource, US government resource
    • pwn.watchpwn.watch: Mitel MiVoice Connect: 2 exploited vulnerabilities (CVE-2022-40765, CVE-2022-41223)pwn-watch
    • NVD (NIST)NVD: CVE-2022-40765pwn-watch
    • mitel.comVendor advisory: Mitel MiVoice Connectpwn-watch
    • NVD (NIST)NVD: CVE-2022-41223pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2022-40765
    <a href="https://intel.neosec.eu/en/cve/CVE-2022-40765"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-40765.svg?lang=en" alt="CVE-2022-40765 – NEOSEC Intel" height="20"></a>