dbcve.org
MicollabApplication · Mitel

CVE-2024-47189

HIGH · 7.7 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to after 9.8.1.201 or later.
See remediation →
86/100
Remediation priority · High
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 API Interface of the AWV (Audio, Web and Video Conferencing) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could allow an unauthenticated attacker to conduct SQL injection due to insufficient sanitization of user input. A successful exploit could allow an attacker with knowledge of specific details to access non-sensitive user provisioning information and execute arbitrary SQL database 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 · moderate confidence

SQL injection vulnerability in the API Interface of the AWV (Audio, Web and Video Conferencing) component of Mitel MiCollab allows unauthenticated attackers to inject malicious SQL code through insufficiently sanitized user input. Successful exploitation enables access to non-sensitive user provisioning information and potentially execution of arbitrary SQL database commands.

MitigationApply vendor patches (Mitel MiCollab 9.8 SP1 FP2 or later), implement parameterized queries/prepared statements for all database interactions, and consider WAF rules to detect and block SQL injection attempts until patching is complete.

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.8.1.201

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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 if Mitel MiCollab is installed
    Check for MiCollab installation directories, services, or application listings. Common locations include /opt/mitel/micollab or Windows Program Files. Use 'ls' or 'Get-Process' commands to locate running MiCollab processes.
    Affected if MiCollab software is present in the environment
  2. Determine the installed MiCollab version
    Check the version number through the administrative web interface (typically at /mc root path), the Windows service information, or by running: 'rpm -q micollab' on Linux or checking the application properties on Windows. Compare the version to 9.8.1.201.
    Affected if Installed version is 9.8.1.201 or lower
  3. Verify the AWV (Audio, Web and Video Conferencing) component is enabled
    Access the MiCollab administrative console and navigate to the AWV component settings. Check if the AWV API Interface is accessible and enabled for user connections. This is typically found under Services or Conferencing settings.
    Affected if AWV component is enabled and the API Interface is accessible
  4. Identify exposed AWV API endpoints
    Check network listening services on the MiCollab server for ports associated with AWV (typically ports 443, 8080, or 8443 for web services). Examine the web server configuration to locate AWV API paths such as /awv/api/ or /api/conferencing/.
    Affected if AWV API endpoints are exposed and reachable over the network

If MiCollab version 9.8.1.201 or lower is installed with the AWV API Interface enabled and exposed, the environment is affected by this SQL injection vulnerability.

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

Apply vendor patches (Mitel MiCollab 9.8 SP1 FP2 or later), implement parameterized queries/prepared statements for all database interactions, and consider WAF rules to detect and block SQL injection attempts until patching is complete.

Recommended fix Moderate confidence

any version newer than 9.8.1.201 (obtain exact patched release from Mitel)

  1. Identify the current Mitel MiCollab version deployed in your environment
  2. Contact Mitel technical support or visit their security advisory portal to obtain the specific patched release newer than 9.8.1.201
  3. Schedule a maintenance window for the upgrade
  4. Backup all critical configurations and data before proceeding
  5. Upgrade MiCollab to the patched version provided by Mitel
  6. After upgrade, verify the installed version matches the patched release
  7. Test the AWV (Audio, Web and Video Conferencing) API functionality to confirm normal operation
  8. Review logs for any SQL injection attempts or anomalies
Caveat review Mitel upgrade documentation for version-specific changes or known issues

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-2024-47189 — 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-2024-47189 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