CVE-2017-16250
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 Mitel ST 14.2, release GA28 and earlier, could allow an attacker to use the API function to enumerate through user-ids which could be used to identify valid user ids and associated user names.
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 confidenceMitel ST 14.2 and earlier versions contain an API that exposes user enumeration by allowing attackers to iterate through user-ids to discover valid user accounts and associated usernames. This information disclosure could facilitate brute-force attacks or credential stuffing.
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<= ga28CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Mitel ST installationLocate Mitel ST software on the system by checking for the application directory, service, or web interface typically accessible on standard HTTP/HTTPS portsAffected if Mitel ST software is found running on the system
-
Determine installed versionAccess the Mitel ST admin interface or check the software documentation for version information, then compare the exact version number against the affected range (14.2 and earlier, specifically <= ga28)Affected if Installed version is 14.2 or earlier, or specifically ga28 or lower
-
Locate the API endpointIdentify if the Mitel ST API is accessible by checking for web service endpoints at common paths such as /api/, /webservices/, or as documented in the product API referenceAffected if The API endpoint is reachable over the network without authentication
-
Test for user enumeration vulnerabilitySend HTTP requests to the API with sequential or guessable user-id values and analyze whether the responses differentiate between valid and invalid user accounts (valid accounts may return username, profile data, or success responses while invalid accounts return error messages)Affected if The API returns distinct responses that reveal whether a user ID is valid, allowing iteration to enumerate existing accounts
The environment is affected if Mitel ST version 14.2 or earlier (ga28 or lower) is running and the API endpoint is accessible without proper authentication, allowing differentiation between valid and invalid user IDs.
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 dataRestrict API access to authenticated users, implement rate limiting on API endpoints, and modify responses to return generic error messages instead of revealing valid user account existence.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16250 — 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-2017-16250 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