dbcve.org
MicollabApplication · Mitel

CVE-2020-35547

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-29
Fix available
A fix is available. Upgrade to after 9.2 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 library index page in NuPoint Messenger in Mitel MiCollab before 9.2 FP1 could allow an unauthenticated attacker to gain access (view and modify) to user data.

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

NuPoint Messenger in Mitel MiCollab contains an authentication bypass vulnerability in its library index page. An unauthenticated attacker can access this page directly without credentials, allowing them to view and modify user data. The vulnerability affects versions prior to 9.2 FP1.

MitigationUpgrade Mitel MiCollab to version 9.2 FP1 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict network access to the affected service using firewall rules or network segmentation as a temporary compensating control.

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

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
None

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

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 if Mitel MiCollab with NuPoint Messenger is installed
    Check for MiCollab installation directories (typically in /opt/mitel/micollab or C:\Program Files\Mitel\MiCollab) or look for the 'NuPoint Messenger' service running on the system
    Affected if MiCollab or NuPoint Messenger software is present on the system
  2. Determine the installed MiCollab version
    Check the installed version using MiCollab's version information file, typically found in the installation directory, or query the system for the installed package version using system inventory tools
    Affected if The installed version is 9.2 or lower, or the version cannot be determined (treat as vulnerable)
  3. Verify if the NuPoint Messenger library page is accessible without authentication
    Attempt to access the NuPoint Messenger library index page directly via HTTP/HTTPS (typically at /npm/library/ or similar library paths) without providing any credentials
    Affected if The page loads successfully and displays user data or administrative content without requiring login credentials
  4. Check network exposure of the NuPoint Messenger service
    Determine if the NuPoint Messenger web interface is exposed to untrusted networks by reviewing firewall rules, listening ports, and network configuration
    Affected if The service is accessible from untrusted network segments or the internet

A system is affected if Mitel MiCollab version 9.2 or lower is installed and the NuPoint Messenger library page can be accessed directly without authentication.

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

Upgrade Mitel MiCollab to version 9.2 FP1 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict network access to the affected service using firewall rules or network segmentation as a temporary compensating control.

Recommended fix High confidence

Mitel MiCollab 9.2 FP1 (Feature Pack 1)

  1. Verify current MiCollab version through the administration interface or system information
  2. Download Mitel MiCollab version 9.2 FP1 or later from the official Mitel support portal
  3. Review Mitel upgrade documentation and release notes for MiCollab 9.2 FP1
  4. Schedule a maintenance window to perform the upgrade
  5. Create a complete backup of the current MiCollab system configuration and data
  6. Follow Mitel official upgrade procedures to install version 9.2 FP1
  7. After upgrade, verify that the NuPoint Messenger component is functioning correctly
  8. Confirm the vulnerability is remediated by testing access to the library index page

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

Fix this in Micollab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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