dbcve.org
Mivoice ConnectApplication · Mitel

CVE-2020-10211

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-17
Fix available
A fix is available. Upgrade to 22.11.4900.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 remote code execution vulnerability in UCB component of Mitel MiVoice Connect before 19.1 SP1 could allow an unauthenticated remote attacker to execute arbitrary scripts due to insufficient validation of URL parameters. A successful exploit could allow an attacker to gain access to sensitive information.

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

A remote code execution vulnerability in the UCB component of Mitel MiVoice Connect (versions prior to 19.1 SP1) allows unauthenticated remote attackers to execute arbitrary scripts due to insufficient validation of URL parameters. Successful exploitation grants access to sensitive information.

MitigationApply Mitel MiVoice Connect version 19.1 SP1 or later to remediate this vulnerability.

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:< 22.11.4900.0

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

CVSS:3.1/AV:N/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 Mitel MiVoice Connect installation
    Locate the Mitel MiVoice Connect installation directory or check for running services related to Mitel Connect on the system. Look for service names containing 'Mitel' or 'MiVoice' in Windows Services or running processes.
    Affected if Mitel MiVoice Connect is installed and running
  2. Determine installed MiVoice Connect version
    Check the version of MiVoice Connect installed. This can typically be found in the application itself under Help > About, or in the Windows Programs and Features list, or by querying the Mitel service information.
    Affected if Installed version is lower than 22.11.4900.0
  3. Verify UCB component is accessible
    Check if the UCB component is enabled and accessible on the system. The UCB component is typically accessed via web interface. Attempt to access the UCB endpoint or check configuration files for UCB component status.
    Affected if UCB component is enabled and exposed via network
  4. Check for unauthenticated access to UCB URLs
    Review network accessible URLs for the UCB component. The vulnerability exploits insufficient validation of URL parameters. Check if the UCB web interface allows unauthenticated access.
    Affected if UCB web interface is accessible without authentication

A system is affected if it runs Mitel MiVoice Connect with version lower than 22.11.4900.0 and has the UCB component enabled and network-accessible.

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 22.11.4900.0 or later
Fixed in 22.11.4900.0
Interim mitigation

Apply Mitel MiVoice Connect version 19.1 SP1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Mitel MiVoice Connect 22.11.4900.0 or later

  1. 1. Identify current Mitel MiVoice Connect version by accessing the admin console or checking system documentation
  2. 2. Confirm the installed version is below 22.11.4900.0
  3. 3. Download Mitel MiVoice Connect version 22.11.4900.0 or later from the official Mitel support portal (www.mitel.com)
  4. 4. Review Mitel upgrade documentation and release notes for the target version
  5. 5. Schedule a maintenance window as upgrades may require system downtime
  6. 6. Perform a complete backup of the MiVoice Connect system configuration and database
  7. 7. Follow Mitel's official upgrade procedure for MiVoice Connect
  8. 8. After upgrade, verify the UCB component is functioning correctly
Caveat Upgrade may require downtime; ensure compatibility with existing integrations and review release notes for any configuration changes

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

Fix this in Mivoice Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10211 — 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-2020-10211 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