CVE-2020-27340
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 · uneditedThe online help portal of Mitel MiCollab before 9.2 could allow an attacker to redirect a user to an unauthorized website by executing malicious script due to insufficient access control.
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 confidenceAn open redirect vulnerability exists in the online help portal of Mitel MiCollab before version 9.2. Attackers can craft malicious URLs containing arbitrary redirect destinations that the help portal will follow due to insufficient validation of redirect parameters, allowing phishing or unauthorized website redirection attacks.
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< 9.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed MiCollab versionAccess the MiCollab administration interface or check system inventory/asset management for the installed MiCollab version number. Common locations include the server management console, software inventory, or the help/about section of the admin portal.Affected if The installed version is any release before 9.2 (e.g., 9.1, 9.0, older versions).
-
Identify if help portal is accessibleLocate the URL for the MiCollab online help portal - typically found at /help, /portal/help, or similar path on the MiCollab server. Attempt to access this endpoint from a browser or via curl to confirm it is reachable.Affected if The help portal is publicly or internally accessible on the network.
-
Test redirect parameter for open redirect vulnerabilityConstruct a test URL by appending a redirect parameter to the help portal URL (for example: https://[server]/help?url=https://example.com or https://[server]/help?redirect=https://example.com). Observe whether the browser or HTTP client automatically redirects to the arbitrary domain specified.Affected if The help portal redirects to an untrusted or arbitrary domain when a crafted redirect parameter is provided, indicating the vulnerability is present.
Your environment is affected if MiCollab version is below 9.2 AND the help portal is accessible AND the redirect parameter allows arbitrary external URLs.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data9.2
Upgrade Mitel MiCollab to version 9.2 or later which contains the fix for this open redirect vulnerability. If immediate patching is not possible, implement URL validation at the application or proxy layer to restrict redirect destinations to trusted domains.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27340 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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