dbcve.org
MicollabApplication · Mitel

CVE-2024-35286

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to after 9.8.0.33 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
A vulnerability in NuPoint Messenger (NPM) of Mitel MiCollab through 9.8.0.33 allows an unauthenticated attacker to conduct a SQL injection attack due to insufficient sanitization of user input. A successful exploit could allow an attacker to access sensitive information and execute arbitrary database and management operations.

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

A SQL injection vulnerability in NuPoint Messenger (NPM) of Mitel MiCollab through version 9.8.0.33 allows unauthenticated attackers to inject malicious SQL queries through insufficiently sanitized user input fields, potentially exposing sensitive data and enabling arbitrary database command execution.

MitigationApply vendor patch 9.8.0.34 or later immediately. Until patch is deployed, consider network segmentation and web application firewall rules to mitigate exploitation risk.

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

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 if MiCollab is installed
    Check system for MiCollab installation by looking for installation directories, services, or the web interface. Common paths include /opt/mitel/micollab or check for the 'micollab' service running.
    Affected if MiCollab software is not found on the system, the user is not affected by this CVE.
  2. Determine installed MiCollab version
    Locate the MiCollab version information - typically found in the web interface (often at /micollab or /npm), in installation logs, or via command line tools provided by Mitel. Compare the version number to the affected range.
    Affected if The installed version is 9.8.0.33 or lower, the environment is within the affected range.
  3. Verify NuPoint Messenger component status
    Check if the NuPoint Messenger (NPM) component is accessible or enabled within MiCollab. This is typically accessible via the web interface on port 443 or 8443, often under paths like /npm or /micollab/npm.
    Affected if NuPoint Messenger component is active and reachable, it may be vulnerable to SQL injection if the version is within the affected range.
  4. Check web interface exposure
    Review network configuration to determine if the MiCollab/NPM web interface is accessible from untrusted networks. Check firewall rules, reverse proxy configurations, or cloud security groups.
    Affected if The NPM web interface is exposed to unauthenticated network access, exploitation becomes possible.

A user is affected if MiCollab with NuPoint Messenger component is installed at version 9.8.0.33 or lower 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 9.8.0.33
Interim mitigation

Apply vendor patch 9.8.0.34 or later immediately. Until patch is deployed, consider network segmentation and web application firewall rules to mitigate exploitation risk.

Recommended fix Moderate confidence

Any Mitel MiCollab version newer than 9.8.0.33 (contact Mitel for exact fixed release number)

  1. 1. Identify the current version of Mitel MiCollab (NuPoint Messenger) installed in your environment
  2. 2. Contact Mitel support or check Mitel's security advisory page at www.mitel.com for the specific fixed release version
  3. 3. Plan the upgrade during a maintenance window to minimize business impact
  4. 4. Before upgrading, backup the current configuration and database
  5. 5. Download and install the Mitel MiCollab version newer than 9.8.0.33 (the fixed release)
  6. 6. After upgrade, verify that the NuPoint Messenger component is functioning correctly
  7. 7. Validate that the SQL injection vulnerability is remediated by confirming the fix or running authenticated penetration tests if available
Caveat Check Mitel release notes for any configuration or feature changes between your current version and the fixed version

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