CVE-2016-6562
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 · uneditedOn iOS and Android devices, the ShoreTel Mobility Client app version 9.1.3.109 fails to properly validate SSL certificates provided by HTTPS connections, which means that an attacker in the position to perform MITM attacks may be able to obtain sensitive account information such as login credentials.
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 confidenceThe ShoreTel Mobility Client app version 9.1.3.109 for iOS and Android fails to properly validate SSL certificates during HTTPS connections, allowing an attacker performing a man-in-the-middle (MITM) attack to intercept sensitive authentication credentials transmitted by the app.
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.1.3.109CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:N/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 ShoreTel Mobility Client on iOS devicesCheck iOS devices by going to Settings > General > iPhone Storage (or iPad Storage), or use MDM/EMM software to enumerate installed apps. Look for an app named ShoreTel Mobility Client or Mitel ShoreTel Mobility Client.Affected if The app is present on any iOS device in the environment
-
Identify ShoreTel Mobility Client on Android devicesCheck Android devices by navigating to Settings > Apps > Apps, or use MDM/EMM software to enumerate installed applications. Look for an app named ShoreTel Mobility Client or Mitel ShoreTel Mobility Client.Affected if The app is present on any Android device in the environment
-
Determine the installed version numberFor iOS: In Settings > General > iPhone Storage, tap on ShoreTel Mobility Client to view the Version number. For Android: In Settings > Apps > [App Name], tap on App info to view the Version. Alternatively, query via MDM/EMM console or mobile device management reports.Affected if The version displayed is exactly 9.1.3.109
-
Verify the vulnerability appliesThe vulnerability exists in version 9.1.3.109 due to improper SSL certificate chain and hostname validation. This specific version does not validate SSL certificates properly when transmitting authentication credentials over HTTPS.Affected if The installed version is exactly 9.1.3.109 and the app is used to transmit authentication credentials over HTTPS networks
If the ShoreTel Mobility Client version 9.1.3.109 is installed on any iOS or Android device in the environment, the improper SSL certificate validation vulnerability is present and sensitive authentication credentials could be intercepted via MITM attacks.
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 dataUpdate to a patched version of the ShoreTel Mobility Client that implements proper SSL certificate chain and hostname validation. Until patched, users should avoid using the app on untrusted networks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6562 — 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-2016-6562 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