dbcve.org
Mivoice ConnectApplication · Mitel

CVE-2023-31460

HIGH · 7.2 CVSS v3.1 Published 2023-05-24
Fix available
A fix is available. Upgrade to after 9.6.2208.101 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the Connect Mobility Router component of MiVoice Connect versions 9.6.2208.101 and earlier could allow an authenticated attacker with internal network access to conduct a command injection attack due to insufficient restriction on URL parameters.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a command injection vulnerability in the Connect Mobility Router component of MiVoice Connect. An authenticated attacker with internal network access can inject arbitrary commands through unsanitized URL parameters, allowing execution of OS-level commands on the affected system.

MitigationUpdate MiVoice Connect to a version beyond 9.6.2208.101 that includes the security patch. If immediate patching is not possible, implement strict input validation on all URL parameters and restrict network access to the Connect Mobility Router to trusted internal users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mivoice ConnectApplication
Affected:<= 9.6.2208.101

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate MiVoice Connect installation and version
    Check your system for MiVoice Connect installation directory or use system inventory tools to identify the installed Mitel software version. Look for Mitel-specific directories, services, or the Mitel Mobility Router application.
    Affected if The installed version is 9.6.2208.101 or lower, indicating it falls within the affected version range.
  2. Verify Connect Mobility Router component
    Inspect the MiVoice Connect configuration or services list to confirm whether the Connect Mobility Router component is installed and running. Check for Mobility Router processes, services, or web interface availability.
    Affected if The Connect Mobility Router component is present and active on the system.
  3. Confirm network accessibility of Mobility Router
    Test connectivity to the Mobility Router web interface or API endpoints from internal network segments. Check firewall rules, network ACLs, or port configurations that allow access to typical Mobility Router ports (commonly 443, 8443, or as configured).
    Affected if The Mobility Router is reachable over the network from non-trusted internal segments, making it accessible to potential attackers.
  4. Check authentication configuration
    Review user authentication settings for the Connect Mobility Router. Determine if default or weak credentials are in use, or if the authentication mechanism allows internal network users to access the router interface.
    Affected if The Mobility Router accepts authentication from internal network users without sufficient access controls, allowing an authenticated attacker to reach the vulnerable parameter input points.

Your environment is affected if MiVoice Connect version is 9.6.2208.101 or lower AND the Connect Mobility Router component is enabled and accessible to authenticated internal users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.6.2208.101
Interim mitigation

Update MiVoice Connect to a version beyond 9.6.2208.101 that includes the security patch. If immediate patching is not possible, implement strict input validation on all URL parameters and restrict network access to the Connect Mobility Router to trusted internal users only.

Recommended fix Moderate confidence

Contact Mitel for the specific fixed release (version > 9.6.2208.101)

  1. Identify the current MiVoice Connect version installed in your environment
  2. Contact Mitel support or check Mitel security advisories to obtain the specific fixed release version that addresses CVE-2023-31460
  3. Plan and schedule an upgrade to a version newer than 9.6.2208.101 following Mitel's standard upgrade procedures
  4. After upgrading, verify that the Connect Mobility Router component has been updated and test that command injection is no longer possible
  5. Document the upgrade for audit and compliance purposes
Caveat Review Mitel release notes for the target version for any compatibility or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mivoice Connect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31460 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data