dbcve.org
MicollabApplication · Mitel

CVE-2019-12165

CRITICAL · 9.8 CVSS v3.1 Published 2019-05-29
Fix available
A fix is available. Upgrade to after 7.3.0.204 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
MiCollab 7.3 PR2 (7.3.0.204) and earlier, 7.2 (7.2.2.13) and earlier, and 7.1 (7.1.0.57) and earlier and MiCollab AWV 6.3 (6.3.0.103), 6.2 (6.2.2.8), 6.1 (6.1.0.28), 6.0 (6.0.0.61), and 5.0 (5.0.5.7) have a Command Execution Vulnerability. Successful exploit of this vulnerability could allow an attacker to execute arbitrary system commands.

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

Unauthenticated command injection vulnerability in MiCollab and MiCollab AWV web interfaces allows remote attackers to execute arbitrary system commands via specially crafted requests, likely due to insufficient input validation on user-supplied parameters.

MitigationApply vendor-provided patches for all affected MiCollab versions (7.3 PR2 and earlier, 7.2 and earlier, 7.1 and earlier) and MiCollab AWV versions (6.3, 6.2, 6.1, 6.0, 5.0). If patching is delayed, restrict external network access to the application interfaces.

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:>= 7.1, <= 7.1.0.57>= 7.2, <= 7.2.2.13>= 7.3, <= 7.3.0.204
Micollab Audio\, Web \& Video ConferencingApplication
Affected:>= 5.0, <= 5.0.5.7>= 6.0, <= 6.0.0.61>= 6.1, <= 6.1.0.28>= 6.2, <= 6.2.2.8>= 6.3, <= 6.3.0.103

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
High

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

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 and version
    Check for MiCollab installation directories or running services. Common locations include /opt/mitel/micollab or C:\Program Files\Mitel\MiCollab. Query the system for MiCollab services and retrieve the installed version from service information or version files within the installation directory.
    Affected if The installed version falls within any of these ranges: 7.1.0 through 7.1.0.57, 7.2.0 through 7.2.2.13, or 7.3.0 through 7.3.0.204.
  2. Identify MiCollab AWV installation and version
    Check for MiCollab Audio, Web & Video Conferencing installation. Query the system for AWV-related services or check common installation paths. Retrieve the version from service information or version files within the installation directory.
    Affected if The installed version falls within any of these ranges: 5.0.0 through 5.0.5.7, 6.0.0 through 6.0.0.61, 6.1.0 through 6.1.0.28, 6.2.0 through 6.2.2.8, or 6.3.0 through 6.3.0.103.
  3. Verify web interface is accessible
    Confirm that the MiCollab or MiCollab AWV web interface is reachable. Check if HTTP/HTTPS services are listening on typical ports such as 80, 443, 8080, or 8443. Verify the web application is exposed by attempting to access the login page or by reviewing network listener configuration.
    Affected if The web interface is exposed and reachable on network ports.
  4. Review web interface exposure
    Determine if the web interface is accessible from external networks or untrusted zones. Check firewall rules, reverse proxy configurations, and network ACLs that govern access to the MiCollab web ports.
    Affected if The web interface is accessible from untrusted networks or the internet.

You are affected if MiCollab or MiCollab AWV is installed with a version matching any of the affected ranges and the web interface is network-accessible.

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 7.3.0.204
Interim mitigation

Apply vendor-provided patches for all affected MiCollab versions (7.3 PR2 and earlier, 7.2 and earlier, 7.1 and earlier) and MiCollab AWV versions (6.3, 6.2, 6.1, 6.0, 5.0). If patching is delayed, restrict external network access to the application interfaces.

Recommended fix Moderate confidence

MiCollab 7.3.0.205+ or latest 7.x release; MiCollab AWV 6.3.0.104+ or latest 6.x release

  1. 1. Identify the currently installed MiCollab version from the system administration console or command line.
  2. 2. For MiCollab version 7.x: Upgrade to version 7.3.0.205 or later (or the latest available 7.x release).
  3. 3. For MiCollab Audio, Web & Video Conferencing version 6.x: Upgrade to version 6.3.0.104 or later (or the latest available 6.x release).
  4. 4. For MiCollab Audio, Web & Video Conferencing version 5.x: Upgrade to version 5.0.5.8 or later, or migrate to a supported 6.x/7.x version.
  5. 5. Schedule the upgrade during a maintenance window and take a complete backup of the system first.
  6. 6. After upgrading, verify the system is functioning correctly and test that the vulnerability is no longer present.
Caveat Review MiCollab release notes for any compatibility changes or required migration steps before upgrading

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
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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