CVE-2020-13767
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 Mitel MiCollab application before 9.1.332 for iOS could allow an unauthorized user to access restricted files and folders due to insufficient access control. An exploit requires a rooted iOS device, and (if successful) could allow an attacker to gain access to sensitive information,
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 confidenceThe Mitel MiCollab iOS application before version 9.1.332 contains insufficient access control mechanisms that allow unauthorized access to restricted files and folders on the device. An attacker with a rooted or jailbroken iOS device can exploit this to access sensitive information stored within the application.
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.1.332CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MiCollab iOS app is installedOn the iOS device, go to Settings > General > iPhone Storage (or iPad Storage). Scroll down the list of installed applications and look for 'MiCollab' or 'Mitel MiCollab'.Affected if MiCollab appears in the installed applications list
-
Identify the installed MiCollab versionIn Settings > General > iPhone Storage, tap on MiCollab. The version number is displayed below the app name (typically shown as a build number or version like '9.x.x').Affected if A version number is displayed for MiCollab
-
Compare version against the vulnerable thresholdCompare the installed version number to 9.1.332. Note that versions below 9.1.332 are affected; version 9.1.332 and later are patched.Affected if The displayed version number is lower than 9.1.332 (for example, 9.0.100, 9.1.0, etc.)
-
Verify iOS jailbreak status (optional context)Check if the device has been jailbroken by looking for Cydia, Sileo, or other unauthorized app stores in the app drawer, or by using a jailbreak detection utility from the App Store.Affected if The device is jailbroken AND MiCollab version is below 9.1.332 (exploitation requires jailbroken device)
A user is affected if the Mitel MiCollab iOS application is installed with a version number lower than 9.1.332 on a jailbroken iOS device.
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.1.332
Update MiCollab for iOS to version 9.1.332 or later to obtain the patched version with proper access controls.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13767 — 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-13767 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