# CVE-2017-5250: Information disclosure in Insteon for Hub

> Attackers can access unencrypted OAuth tokens from the Insteon Hub Android app, potentially leading to unauthorized account access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wwpq-7cfc-wwwm

## What is CVE-2017-5250?

CVE-2017-5250 is a critical vulnerability in Insteon for Hub, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In version 1.9.7 and prior of Insteon's Insteon for Hub Android app, the OAuth token used by the app to authorize user access is not stored in an encrypted and secure manner.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2017-5250?

It affects 1 product.


Products: Insteon Insteon for Hub.

## How do I fix CVE-2017-5250?

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

## Is CVE-2017-5250 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5250 and fix it if it is affected.

What it is: CVE-2017-5250 is a critical vulnerability in Insteon for Hub, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5250 in the wild and no public exploit code.

Affected product: Insteon for Hub. 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-2017-5250/ (Markdown: https://insights.sbomify.com/CVE-2017-5250/index.md)
```

## Sources

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

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