CVE-2023-39289
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 in the Connect Mobility Router component of Mitel MiVoice Connect through 9.6.2208.101 could allow an unauthenticated attacker to conduct an account enumeration attack due to improper configuration. A successful exploit could allow an attacker to access system 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 · high confidenceThis is an account enumeration vulnerability in Mitel MiVoice Connect's Connect Mobility Router. An unauthenticated attacker can exploit improper configuration to determine valid user accounts by observing different system responses, potentially gaining system information that could aid further attacks.
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<= 9.6.2208.101CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify MiVoice Connect installationLocate Mitel MiVoice Connect installation directories or check installed programs on the server. Common paths include C:\Mitel\Connect or /opt/mitel/connect. Use system inventory tools or check Program Files directory on Windows.Affected if MiVoice Connect is installed and the version is 9.6.2208.101 or lower
-
Verify Connect Mobility Router componentConfirm the Connect Mobility Router (CMR) component is present and enabled. Check for CMR service or configuration files in the MiVoice Connect installation directory.Affected if Connect Mobility Router is installed and running as part of MiVoice Connect
-
Check CMR accessibilityDetermine if the Connect Mobility Router web interface or API endpoints are exposed externally. Review firewall rules, reverse proxy configurations, and network ACLs that control access to CMR ports (typically ports 443, 8443, or 48080).Affected if CMR is accessible from untrusted networks without authentication restrictions
-
Test account enumeration response behaviorSend HTTP requests to CMR login endpoints with both valid and invalid username formats. Compare HTTP status codes, response times, and error messages for differences. Common endpoints include /mobility/login or /api/auth.Affected if The system returns measurably different responses (status codes, error messages, or response times) for valid versus invalid account inputs
-
Review authentication configurationExamine CMR configuration files for settings related to error messaging, account lockout, and response standardization. Look for XML or config files in the CMR configuration directory.Affected if Configuration allows distinct error messages for valid vs invalid usernames or lacks uniform response handling
The environment is affected if MiVoice Connect version 9.6.2208.101 or lower is installed with Connect Mobility Router enabled and accessible, and the system returns differentiated responses that could enable account enumeration.
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.
From vendor dataConfigure the Connect Mobility Router to return uniform responses for both valid and invalid account queries, implement rate limiting on authentication endpoints, and apply vendor-recommended hardening configurations.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39289 — 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-2023-39289 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