Security readout for executives and security teams
Plain-English summary
The Wink Smart Home Android app stored its OAuth access token insecurely in version 6.1.0.19 and earlier. That token authorizes access to a user’s Wink account, so exposure could affect control or visibility of connected smart-home devices. The source bundle does not provide CVSS, a fixed version, or confirmed exploitation.
Executive priority
Treat this as a targeted exposure risk, not a confirmed emergency. Prioritize if the organization manages Wink-connected facilities or employee devices using the affected Android app, especially where physical or device compromise risk is realistic.
Technical view
CVE-2017-5249 is a CWE-922 insecure storage issue in Wink Labs’s Android app. The app’s OAuth token was not encrypted or otherwise securely stored. Impact depends on whether an attacker can access the app’s local data or a compromised device. The provided sources do not describe exploit prerequisites, token scope, or remediation details.
Likely exposure
Exposure is limited to Wink - Smart Home Android app deployments at version 6.1.0.19 and prior. Highest concern is unmanaged, rooted, lost, compromised, or backed-up Android devices where app-local secrets may be recoverable.
Exploitation context
The bundle does not show CISA KEV listing or any confirmed active exploitation. Public evidence supports insecure token storage only; it does not establish remote exploitation, exploit availability, or broad campaign activity.
Researcher notes
The CVE record only states insecure OAuth token storage and affected versions. Rapid7 is the cited disclosure source. Avoid assuming the storage location, exploitability from a locked device, token lifetime, or cloud-side privileges without additional vendor or researcher evidence.
Mitigation direction
- Inventory Android devices for Wink app version 6.1.0.19 or earlier.
- Check Wink guidance for fixed versions or account-session reset instructions.
- Update the Wink Android app where vendor-supported updates are available.
- Remove unsupported vulnerable app versions from managed devices.
- If compromise is suspected, follow vendor guidance to revoke sessions or reset credentials.
Validation and detection
- Confirm installed Wink app versions through MDM, EMM, or device inventory.
- Identify devices with higher local-access risk, including rooted or lost devices.
- Review Wink account activity for unauthorized device or account changes.
- Check vendor advisories before declaring a version fixed.
- Document evidence gaps: no CVSS, no fixed version, no KEV listing.
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-5249 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.