dbcve.org
MicollabApplication · Mitel

CVE-2021-27402

MEDIUM · 6.5 CVSS v3.1 Published 2021-08-13
Fix available
A fix is available. Upgrade to 9.2 or later.
See remediation →
74/100
Remediation priority · Elevated
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
The SAS Admin portal of Mitel MiCollab before 9.2 FP2 could allow an unauthenticated attacker to access (view and modify) user data by injecting arbitrary directory paths due to improper URL validation, aka Directory Traversal.

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 directory traversal vulnerability exists in the SAS Admin portal of Mitel MiCollab versions prior to 9.2 FP2. The application fails to properly validate URL inputs, allowing unauthenticated attackers to inject arbitrary directory paths and access or modify sensitive user data outside the intended web root.

MitigationUpgrade to MiCollab version 9.2 FP2 or later, which contains the fix for proper URL validation. If immediate patching is not possible, implement web application firewall (WAF) rules to block directory traversal patterns (e.g., ../, ..\) in URL parameters.

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= 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 MiCollab installation version
    Access the MiCollab admin interface or check system registry/files for the installed MiCollab version number. Common locations include the MiCollab administration console or the software installation directory.
    Affected if The installed version is 9.2 or any version below 9.2 FP2 (for example, 9.1, 9.0, 8.x)
  2. Confirm SAS Admin portal is enabled
    Check if the SAS Admin portal service is running and accessible. This is typically found at /sas/admin or similar paths within the MiCollab web interface.
    Affected if The SAS Admin portal is active and reachable on the network
  3. Check network exposure of admin interface
    Determine if the SAS Admin portal is exposed to untrusted networks. Review firewall rules and access control lists restricting access to the admin portal.
    Affected if The SAS Admin portal is accessible from untrusted networks or the public internet without proper network segmentation
  4. Verify URL input validation behavior
    If accessible, attempt a benign directory traversal test (e.g., ../) in a URL parameter within the SAS Admin portal to observe if the application accepts or blocks such input.
    Affected if The application accepts directory traversal sequences (../ or ..\) in URL parameters without rejecting them

You are affected if MiCollab version is 9.2 or below AND the SAS Admin portal is accessible, since the vulnerability allows unauthenticated directory traversal attacks.

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.2 or later
Fixed in 9.2
Interim mitigation

Upgrade to MiCollab version 9.2 FP2 or later, which contains the fix for proper URL validation. If immediate patching is not possible, implement web application firewall (WAF) rules to block directory traversal patterns (e.g., ../, ..\) in URL parameters.

Recommended fix Moderate confidence

Mitel MiCollab 9.2 FP2

  1. Identify the current MiCollab version deployed in the environment
  2. Backup all MiCollab configuration data and databases according to Mitel backup procedures
  3. Download MiCollab version 9.2 FP2 (or later) from the Mitel support portal (www.mitel.com)
  4. Apply the upgrade following Mitel's official upgrade documentation for MiCollab
  5. After upgrade, verify the SAS Admin portal accepts normal requests but rejects directory traversal attempts (e.g., ../ patterns)
  6. Confirm that the path traversal vulnerability is no longer exploitable

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

Fix this in Micollab Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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