Security readout for executives and security teams
Plain-English summary
Older Insteon for Hub Android app versions stored the OAuth token used to authorize a user in an insecure way. If that token was exposed from a device, an attacker could potentially access the user’s Insteon account without the password.
Executive priority
Treat this as a targeted exposure-management issue, not an internet-wide emergency. Prioritize homes, facilities, or executives still using legacy Insteon Android apps.
Technical view
CVE-2017-5250 is a CWE-922 insecure storage issue in Insteon for Hub Android app version 1.9.7 and prior. The OAuth token used for authorization was not stored encrypted or securely. Sources do not provide CVSS, a fixed version, or detailed exploit prerequisites.
Likely exposure
Exposure is most likely where Android devices still run Insteon for Hub 1.9.7 or earlier, especially unmanaged, shared, lost, compromised, or rooted devices.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The risk depends on access to token material stored by the affected Android app.
Researcher notes
Evidence is limited to insecure OAuth token storage in the Android app. Sources do not provide CVSS, fixed build details, or exploitation evidence. Avoid assuming remote exploitation without device or token access evidence.
Mitigation direction
- Identify Android devices running Insteon for Hub 1.9.7 or earlier.
- Check Insteon guidance and app-store notes for fixed or replacement versions.
- Remove affected app versions from managed devices where possible.
- Rotate or revoke account tokens after suspected device compromise.
- Review smart-home account access for unexpected devices or sessions.
Validation and detection
- Inventory installed Insteon for Hub Android app versions.
- Confirm whether any devices run version 1.9.7 or earlier.
- Check MDM, endpoint, or helpdesk records for affected installations.
- Review account activity for unusual access after device loss or compromise.
- Verify current app builds use secure encrypted token storage.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-922: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-5250 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://blog.rapid7.com/2017/09/22/multiple-vulnerabilities-in-wink-and-insteon-smart-home-systems/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insecure Storage of Sensitive Information
Insecure Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.