CVE-2020-11797
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 · uneditedAn Authentication Bypass vulnerability in the Published Area of the web conferencing component of Mitel MiCollab AWV before 8.1.2.4 and 9.x before 9.1.3 could allow an unauthenticated attacker to gain access to unauthorized information due to insufficient access validation. A successful exploit could allow an attacker to access sensitive shared files.
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 confidenceMitel MiCollab AWV contains an authentication bypass vulnerability in the web conferencing component's Published Area. The application fails to properly validate access permissions, allowing unauthenticated attackers to directly access sensitive shared files without any credentials. The vulnerability stems from insufficient access control checks on the published file sharing functionality.
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< 8.1.2.4>= 9.0, < 9.1.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/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 AWV installationLocate and identify the Mitel MiCollab Audio, Web and Video (AWV) component in your environment. Check installed applications or running services for MiCollab or related conferencing components.Affected if MiCollab AWV is present on the system
-
Determine installed versionUse system inventory tools, software packages, or the Mitel administration interface to retrieve the exact version number of the MiCollab AWV installation.Affected if Version is less than 8.1.2.4 (for 8.x branch) or greater than or equal to 9.0 but less than 9.1.3
-
Verify Published Area feature existenceCheck if the web conferencing Published Area functionality is enabled or accessible in the MiCollab AWV configuration. This feature allows sharing of files in a published (potentially public) zone.Affected if Published Area feature is enabled or configured
-
Test unauthenticated file accessFrom an external or unauthenticated context, attempt to access the Published Area URL or shared file paths directly without providing credentials. Observe whether the application grants access without authentication.Affected if Unauthenticated access to shared files in Published Area is granted without requiring credentials
User is affected if MiCollab AWV with a vulnerable version (below 8.1.2.4 or 9.0 to below 9.1.3) has the Published Area feature enabled and allows unauthenticated access to shared files.
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 data8.1.2.49.1.3
Upgrade Mitel MiCollab AWV to version 8.1.2.4 or later (for 8.x branch) or 9.1.3 or later (for 9.x branch). Alternatively, if immediate upgrade is not possible, restrict network access to the web conferencing Published Area through firewall rules or network segmentation.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11797 — 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-11797 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