CVE-2024-36446
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 · uneditedThe provisioning manager component of Mitel MiVoice MX-ONE through 7.6 SP1 could allow an authenticated attacker to conduct an authentication bypass attack due to improper access control. A successful exploit could allow an attacker to bypass the authorization schema.
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 confidenceThe provisioning manager component in Mitel MiVoice MX-ONE through version 7.6 SP1 contains an improper access control vulnerability that allows authenticated attackers to bypass the authorization schema. An attacker with valid credentials can exploit this flaw to access resources or perform actions beyond their authorized permissions level.
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< 7.6= 7.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mitel MiVoice MX-ONE installationLocate the MiVoice MX-ONE server or check installed software inventory for the Mitel MiVoice MX-ONE applicationAffected if MiVoice MX-ONE is installed on the system
-
Determine the installed versionCheck the installed version of MiVoice MX-ONE through the system information panel, administration console, or version lookup command provided by the systemAffected if The installed version is 7.6 or any version below 7.6 (including versions prior to 7.6)
-
Verify provisioning manager component statusAccess the provisioning manager interface or check its configuration status through the administration panel to confirm it is enabledAffected if The provisioning manager component is enabled and accessible
-
Check network accessibility of provisioning managerReview network configuration to determine if the provisioning manager interface is exposed to untrusted networks or directly accessible from outside administrative networksAffected if The provisioning manager is exposed to untrusted or non-administrative network segments
-
Audit provisioning manager accounts and permissionsReview user accounts configured in the provisioning manager and verify whether any account has permissions beyond what the user role should normally allowAffected if Any provisioning manager account exists with elevated privileges or permissions that exceed the intended authorization level
A user is affected if MiVoice MX-ONE version 7.6 or below is installed AND the provisioning manager component is enabled and accessible on the network, allowing authenticated users to potentially bypass authorization controls.
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.
dbcve · scoped7.6
Apply the vendor-provided patch for MiVoice MX-ONE 7.6 SP1 or later. If patches are unavailable, restrict network access to the provisioning manager interface to trusted administrative networks and enforce principle of least privilege for all provisioning manager accounts.
MiVoice MX-ONE version > 7.6 (contact Mitel for the specific fixed release)
- Contact Mitel support or visit the official Mitel support portal to obtain the specific patched version for MiVoice MX-ONE
- Verify your current MiVoice MX-ONE version by accessing the system administration interface
- Request and apply the security update/patch for the provisioning manager component
- After patching, verify that the authentication bypass vulnerability in the provisioning manager has been addressed
- Test that the authorization schema functions correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36446 — 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-2024-36446 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