CVE-2017-5249

CRITICALNVD 9.8

9.8

In version 6.1.0.19 and prior of Wink Labs's Wink - Smart Home Android app, the OAuth token used by the app to authorize user access is not stored in an encrypted and secure manner.

CVSS v3: 9.8
EG Score: —
EPSS: 39.0%
KEV: Not listed

Published

February 22, 2018

Last Modified

November 21, 2024

References (2)

cve@rapid7https://blog.rapid7.com/2017/09/22/multiple-vulnerabilities-in-wink-and-insteon-smart-home-systems/
af854a3a-2127-422b-91ae-364da2661108https://blog.rapid7.com/2017/09/22/multiple-vulnerabilities-in-wink-and-insteon-smart-home-systems/

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 12:46 UTCOSV refresh

Frequently asked(5)

What is CVE-2017-5249?

CVE-2017-5249 is a critical vulnerability published on February 22, 2018. In version 6.1.0.19 and prior of Wink Labs's Wink - Smart Home Android app, the OAuth token used by the app to authorize user access is not stored in an encrypted and secure manner.

When was CVE-2017-5249 disclosed?

CVE-2017-5249 was first published in the National Vulnerability Database on February 22, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-5249 actively exploited?

CVE-2017-5249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-5249?

CVE-2017-5249 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-5249?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5249

Explore →

Is Your Infrastructure Affected by CVE-2017-5249?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2017-5249

📅 Published

🔄 Last Modified

🔗 References (2)