dbcve.org
MicollabApplication · Mitel

CVE-2024-35314

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to after 9.7.1.110 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 vulnerability in the Desktop Client of Mitel MiCollab through 9.7.1.110, and MiVoice Business Solution Virtual Instance (MiVB SVI) 1.0.0.25, could allow an unauthenticated attacker to conduct a command injection attack due to insufficient parameter sanitization. A successful exploit requires user interaction and could allow an attacker to execute arbitrary scripts.

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

Unauthenticated command injection vulnerability in Mitel MiCollab Desktop Client (through 9.7.1.110) and MiVB SVI (1.0.0.25) due to insufficient parameter sanitization. Attackers can execute arbitrary scripts without authentication but require user interaction to trigger the attack.

MitigationApply vendor patches for MiCollab and MiVB SVI. Until patched, restrict network access to these services and monitor for suspicious script execution patterns.

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
MicollabApplication
Affected:<= 9.7.1.110
Mivoice Business Solution Virtual InstanceApplication
Affected:= 1.0.0.25

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 MiCollab Desktop Client installation and version
    Check the installed version of Mitel MiCollab Desktop Client. On Windows, check Add/Remove Programs or the application's About/Help section. On Linux, check package manager listings or the installation directory for version files.
    Affected if The installed version is 9.7.1.110 or any earlier version (any version <= 9.7.1.110)
  2. Identify MiVB SVI installation and version
    Check the installed version of Mitel MiVoice Business Solution Virtual Instance. Look for version information in the application, installation directory, or system services listing.
    Affected if The installed version is exactly 1.0.0.25
  3. Verify network exposure of MiCollab services
    Identify which network ports and interfaces MiCollab Desktop Client services are bound to. Check firewall rules and listening services on the host to determine if the application is accessible from untrusted networks.
    Affected if MiCollab services are exposed to untrusted networks or the internet without proper access controls
  4. Verify network exposure of MiVB SVI services
    Identify which network ports and interfaces MiVB SVI is bound to. Check firewall rules and listening services to determine if the application is accessible from untrusted networks.
    Affected if MiVB SVI services are exposed to untrusted networks or the internet without proper access controls
  5. Review for suspicious script execution
    Review system logs, process monitoring, and application logs for unexpected script execution, especially scripts with unusual arguments or scripts spawned from the MiCollab/MiVB processes. Check for unauthorized file creation in script directories.
    Affected if Unexpected or unauthorized script execution is observed, particularly in association with MiCollab or MiVB processes

A system is affected if it runs MiCollab Desktop Client version 9.7.1.110 or earlier, or MiVB SVI version 1.0.0.25, and these services are network-accessible to attackers who could trick a user into triggering the malicious request.

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.7.1.110
Interim mitigation

Apply vendor patches for MiCollab and MiVB SVI. Until patched, restrict network access to these services and monitor for suspicious script execution patterns.

Recommended fix Moderate confidence

MiCollab: version higher than 9.7.1.110 (contact Mitel for exact fixed release) | MiVoice Business Solution Virtual Instance: version higher than 1.0.0.25

  1. Contact Mitel technical support to obtain the specific patched version for MiCollab and MiVoice Business Solution Virtual Instance
  2. Request and apply the latest security update from Mitel that addresses CVE-2024-35314
  3. After patching, verify the fix by reviewing release notes or consulting with Mitel to confirm the command injection vulnerability is resolved
  4. Test the updated Desktop Client to ensure normal functionality is maintained

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

Fix this in Micollab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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