CVE-2017-5250
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 · uneditedIn 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.
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 confidenceThe Insteon for Hub Android app (versions 1.9.7 and prior) stores OAuth authentication tokens in an insecure, unencrypted manner on the device. This allows any malicious app with root access or a local attacker to extract the OAuth tokens and impersonate the legitimate user, gaining unauthorized access to their Insteon smart home account and device controls.
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<= 1.9.7CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 the installed Insteon for Hub app versionOpen the Google Play Store app, search for Insteon for Hub, and view the version number under the app listing. Alternatively, go to Settings > Apps > Insteon for Hub on the device to see the version.Affected if The installed version is 1.9.7 or any version lower than 1.9.7 (1.9.7, 1.9.6, 1.9.5, etc.)
-
Determine if OAuth token storage is unencryptedWith root access on the device, navigate to /data/data/com.insteonhub.android/shared_prefs/ and examine the SharedPreferences XML files for any stored OAuth tokens, access tokens, refresh tokens, or auth tokens. Also check /data/data/com.insteonhub.android/databases/ for any SQLite databases containing token data.Affected if OAuth tokens are found stored in plain text within SharedPreferences files, SQLite databases, or other unencrypted local storage files within the app's data directory.
A user is affected if the Insteon for Hub app version installed on their Android device is 1.9.7 or earlier AND OAuth tokens are stored in an unencrypted format in the app's local storage.
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 dataImplement secure token storage using Android Keystore-backed EncryptedSharedPreferences or similar cryptographic protection mechanisms to ensure OAuth tokens are encrypted at rest. Rotate any tokens that may have been exposed and consider implementing token expiration and refresh mechanisms.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5250 — 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-5250 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