# CVE-2016-6562: Security feature bypass in Mobility Client Andoid

> Attackers can intercept HTTPS traffic to steal login credentials due to improper SSL certificate validation in the ShoreTel Mobility Client mobile app.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gp9v-8hxx-pqxm

## What is CVE-2016-6562?

CVE-2016-6562 is a high-severity vulnerability in ShoreTel Mobility Client Andoid, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2016-6562?

It affects 1 product.


Products: Mitel Shortel Mobility Client.

## How do I fix CVE-2016-6562?

No fix has been published for CVE-2016-6562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6562 being exploited?

There is no known exploitation of CVE-2016-6562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6562 and fix it if it is affected.

What it is: CVE-2016-6562 is a high-severity vulnerability in ShoreTel Mobility Client Andoid, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6562 in the wild and no public exploit code.

Affected product: ShoreTel Mobility Client Andoid. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6562/ (Markdown: https://insights.sbomify.com/CVE-2016-6562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6562
- OSV: https://osv.dev/vulnerability/CVE-2016-6562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6562/
Summaries are generated and may contain mistakes; the official description above is the record.