MicollabApplication · Mitel

CVE-2022-36452

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-25
Fix available
A fix is available. Upgrade to 9.6 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 web conferencing component of Mitel MiCollab through 9.5.0.101 could allow an unauthenticated attacker to upload malicious files. A successful exploit could allow an attacker to execute arbitrary code within the context of the application.

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

Mitel MiCollab versions up to 9.5.0.101 contain an unauthenticated file upload vulnerability in the web conferencing component. An attacker can upload malicious files without authentication, leading to arbitrary code execution within the application context.

MitigationApply vendor-supplied patches or update to a patched version of MiCollab. If immediate patching is not possible, restrict network access to the web conferencing component from untrusted sources.

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.6

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 installation version
    Locate the MiCollab version through the administrative web interface, system information panel, or installation documentation. Common locations include the About section in the admin console or system health/status pages.
    Affected if The installed version is lower than 9.6 (any version up to and including 9.5.0.101 is affected)
  2. Confirm web conferencing component is enabled
    Access the MiCollab administrative interface and locate the web conferencing or meeting conference settings. Verify whether the web conferencing feature is currently activated.
    Affected if The web conferencing component is enabled and accessible
  3. Verify web conferencing accessibility
    Determine if the web conferencing web interface (typically accessible via HTTP/HTTPS on standard web ports) is reachable from the network. Check firewall rules and network configurations that govern access to this service.
    Affected if The web conferencing interface is exposed to network access without proper restrictions
  4. Assess authentication requirements
    Attempt to access the web conferencing upload functionality without providing credentials, or review authentication configuration to confirm whether unauthenticated file uploads are permitted.
    Affected if The file upload functionality in the web conferencing component allows unauthenticated access

You are affected if MiCollab version is below 9.6 AND the web conferencing component is enabled and accessible, allowing unauthenticated file uploads.

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

Apply vendor-supplied patches or update to a patched version of MiCollab. If immediate patching is not possible, restrict network access to the web conferencing component from untrusted sources.

Recommended fix Moderate confidence

Mitel MiCollab 9.6 or later

  1. Verify current MiCollab version by accessing the system administration interface or checking system documentation
  2. Download Mitel MiCollab version 9.6 or later from the official Mitel portal or authorized distribution channel
  3. Review Mitel MiCollab 9.6 release notes for any specific upgrade prerequisites or migration requirements
  4. Create a complete backup of the current MiCollab configuration and database
  5. Schedule a maintenance window to perform the upgrade with minimal business impact
  6. Execute the upgrade following Mitel's official upgrade documentation for MiCollab
  7. After upgrade, verify that the web conferencing component is functioning correctly
  8. Confirm the installed version is 9.6 or later to ensure the vulnerability is patched
Caveat Review 9.6 release notes for any configuration changes or feature modifications that may require adjustment

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

Fix this in Micollab Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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