dbcve.org
Micontact Center BusinessApplication · Mitel

CVE-2023-22854

HIGH · 7.5 CVSS v3.1 Published 2023-02-13
Fix available
A fix is available. Upgrade to 9.4.2.0 or later.
See remediation →
84/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 ccmweb component of Mitel MiContact Center Business server 9.2.2.0 through 9.4.1.0 could allow an unauthenticated attacker to download arbitrary files, due to insufficient restriction of URL parameters. A successful exploit could allow 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 · moderate confidence

A path traversal vulnerability exists in the ccmweb component of Mitel MiContact Center Business versions 9.2.2.0 through 9.4.1.0. The application fails to properly restrict URL parameters, allowing unauthenticated attackers to manipulate file download requests and access arbitrary files on the server. This could expose sensitive system files, configuration data, credentials, or other confidential information.

MitigationApply the vendor-provided patch for the affected MiContact Center Business version. As a compensating control, implement URL parameter validation and restrict file access permissions at the application or network level until the patch can be deployed.

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
Micontact Center BusinessApplication
Affected:>= 9.2.2.0, < 9.4.2.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MiContact Center Business version
    Locate the Mitel MiContact Center Business installation and retrieve the version number (typically via installation directory, registry, or application about/-info page)
    Affected if Installed version is 9.2.2.0 through 9.4.1.0 (versions below 9.4.2.0)
  2. Confirm ccmweb component is accessible
    Determine if the ccmweb web component is exposed by checking if the application web interface is reachable on its typical HTTP/HTTPS ports (consult product documentation for default ports)
    Affected if ccmweb is accessible over the network to unauthenticated users
  3. Verify URL parameter manipulation vulnerability
    Using a browser or HTTP tool, attempt to access files outside the intended directory by manipulating URL parameters in file download requests (for example, using ../ sequences in parameters used for file retrieval)
    Affected if The application returns files from arbitrary system locations when URL parameters are manipulated with path traversal sequences

The environment is affected if MiContact Center Business version is 9.2.2.0 through 9.4.1.0 AND the ccmweb component is accessible AND URL parameter manipulation allows access to files outside the intended directory.

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 9.4.2.0 or later
Fixed in 9.4.2.0
Interim mitigation

Apply the vendor-provided patch for the affected MiContact Center Business version. As a compensating control, implement URL parameter validation and restrict file access permissions at the application or network level until the patch can be deployed.

Recommended fix Moderate confidence

Mitel MiContact Center Business 9.4.2.0

  1. Verify current installation version of MiContact Center Business by accessing the admin console or checking system information
  2. Download MiContact Center Business version 9.4.2.0 or later from the official Mitel download portal
  3. Review Mitel upgrade documentation for MiContact Center Business 9.4.x before proceeding
  4. Schedule a maintenance window as upgrades may require system downtime
  5. Perform a complete backup of the MiContact Center Business database and configuration files
  6. Stop all MiContact Center Business services before upgrading
  7. Install version 9.4.2.0 or later following the official upgrade procedure
  8. Restart services and verify the application is running correctly
Caveat Review Mitel 9.4.x release notes for any configuration or feature changes that may require adjustment; ensure compatibility with existing integrations and third-party applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Micontact Center Business Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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