Mivoice ConnectApplication · Mitel

CVE-2023-31459

HIGH · 8.8 CVSS v3.1 Published 2023-05-24
Fix available
A fix is available. Upgrade to after 9.6.2208.101 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 Mitel MiVoice Connect versions 9.6.2208.101 and earlier could allow an unauthenticated attacker with internal network access to authenticate with administrative privileges, because the initial installation does not enforce a password change. A successful exploit could allow an attacker to make arbitrary configuration changes and execute arbitrary commands.

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 · high confidence

Mitel MiVoice Connect's Connect Mobility Router versions 9.6.2208.101 and earlier fail to enforce a mandatory password change during initial installation. An unauthenticated attacker with internal network access can bypass authentication to obtain administrative privileges, enabling arbitrary configuration changes and command execution.

MitigationImmediately enforce administrative password changes on all MiVoice Connect deployments, implement network segmentation to restrict internal access, and apply vendor patches if available.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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. Identify MiVoice Connect installation version
    Locate the Mitel MiVoice Connect installation and retrieve the version number from the application, typically found in the program files directory, installation logs, or the product's about/status page
    Affected if The installed version is 9.6.2208.101 or earlier (any version at or below 9.6.2208.101)
  2. Determine if this is a fresh or recently installed system
    Review installation timestamps, initial setup completion status, or check whether first-time configuration wizard has been run
    Affected if The system is a fresh installation where the initial setup wizard has not been completed or password enforcement was not triggered
  3. Verify admin password status
    Attempt to access the administrative interface using default credentials or check the authentication configuration to determine if the default administrative password remains unchanged
    Affected if The default admin password has not been changed from the factory default or no mandatory password change was enforced during initial setup
  4. Check authentication configuration
    Inspect the MiVoice Connect authentication settings, specifically looking for whether mandatory password change policies are enabled or enforced during first login
    Affected if Mandatory password change enforcement is disabled or missing from the authentication configuration

You are affected if MiVoice Connect version 9.6.2208.101 or earlier is installed AND the system is in a state where default administrative credentials remain active or password change enforcement was not triggered during initial setup.

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.

From vendor data
Upgrade available Upgrade to a release after 9.6.2208.101
Interim mitigation

Immediately enforce administrative password changes on all MiVoice Connect deployments, implement network segmentation to restrict internal access, and apply vendor patches if available.

Fix this in Mivoice Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-31459 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