CVE-2024-31964
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 · uneditedA vulnerability on Mitel 6800 Series and 6900 Series SIP Phones through 6.3 SP3 HF4, 6900w Series SIP Phone through 6.3.3, and 6970 Conference Unit through 5.1.1 SP8 allows an unauthenticated attacker to conduct an authentication bypass attack due to improper authentication control. A successful exploit could allow an attacker to modify system configuration settings and potentially cause a denial of service.
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 confidenceThis is an authentication bypass vulnerability in Mitel 6800/6900 Series SIP Phones and 6970 Conference Units. An unauthenticated attacker can exploit improper authentication controls to gain unauthorized access to the device management interface, allowing modification of system configuration settings and potential denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Mitel device modelAccess the device web interface or check the device label to confirm it is a Mitel 6800 Series, 6900 Series SIP Phone, or 6970 Conference Unit. This can also be done via SNMP or by logging into the device and checking the system information page.Affected if The device is not one of these model families (6800/6900 Series phones or 6970 Conference Unit), then it is not affected by this CVE.
-
Check the installed firmware versionLog into the device web interface and navigate to the Status or System Information page to view the firmware version. Alternatively, access the device via SSH or console and run the command to display firmware version (often 'show software' or similar).Affected if The installed firmware version is earlier than 6.3 SP3 HF4 for 6800/6900 Series, earlier than 6.3.3 for 6900w Series, or earlier than 5.1.1 SP8 for 6970 Conference Unit.
-
Verify if the web management interface is enabledCheck the device configuration for web server or HTTP/HTTPS management interface settings. This is typically found under the Network or Administration settings in the web UI, or via CLI command like 'show network' or 'show http' depending on the device.Affected if The web management interface is enabled and accessible on the device.
-
Assess network exposure of the management interfaceReview network configuration to determine if the device management interface (HTTP/HTTPS ports 80/443 or admin port) is bound to any IP address accessible from untrusted networks, or check firewall rules protecting the device.Affected if The management interface is reachable from network segments that contain untrusted or external hosts (e.g., directly exposed to the internet or an untrusted VLAN).
The device is likely affected if it is a Mitel 6800/6900 Series phone or 6970 Conference Unit running firmware versions prior to 6.3 SP3 HF4 (6800/6900), 6.3.3 (6900w), or 5.1.1 SP8 (6970), and the device management interface is network-accessible to untrusted users.
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 · scopedApply the vendor-supplied firmware updates (6.3 SP3 HF4 or later for 6800/6900 Series, 6.3.3 or later for 6900w Series, 5.1.1 SP8 or later for 6970 Conference Unit). Until patches are applied, restrict network access to phone management interfaces.
Firmware versions newer than 6.3 SP3 HF4 (6800/6900 Series), 6.3.3 (6900w Series), and 5.1.1 SP8 (6970 Conference Unit) - obtain specific fixed versions from Mitel
- Contact Mitel technical support to obtain the specific firmware updates that address CVE-2024-31964
- Request the fixed firmware versions for 6800/6900 Series SIP Phones (newer than 6.3 SP3 HF4)
- Request the fixed firmware version for 6900w Series SIP Phone (newer than 6.3.3)
- Request the fixed firmware version for 6970 Conference Unit (newer than 5.1.1 SP8)
- Review Mitel security advisory at www.mitel.com for official patch availability
- Apply the firmware update following Mitel's standard upgrade procedures
- Verify the update was applied successfully
- Restrict network access to SIP phone management interfaces to mitigate unauthenticated attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-31964 — 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-31964 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