CVE-2017-5249: 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

Q: How do I fix CVE-2017-5249?

wink: upgrade to newer than 6.1.0.19. Exact commands for each OS are on this page.

Q: Is CVE-2017-5249 being exploited?

CVE-2017-5249 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-5249 affect?

CVE-2017-5249 affects wink. Severity is critical (CVSS 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.

Q: How urgent is CVE-2017-5249?

Priority 54/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-5249 is a critical-severity flaw (CVSS 9.8) affecting wink. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-922, CWE-312
Published	2018-02-22
Last modified	2026-06-17

Publisher (CNA): Rapid7, Inc. · Vendor: wink

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-22 16:29 UTCPublished CVE record published
2026-06-17 01:20 UTCUpdated Record last modified

wink wink UPGRADE

Affected: <= 6.1.0.19

Fixed in: newer than 6.1.0.19

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wink || rpm -q wink || wink --version

2. UPGRADE to newer than 6.1.0.19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wink

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wink

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-5249?

wink: upgrade to newer than 6.1.0.19. Exact commands for each OS are on this page.

Is CVE-2017-5249 being exploited?

CVE-2017-5249 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-5249 affect?

CVE-2017-5249 affects wink. Severity is critical (CVSS 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.

How urgent is CVE-2017-5249?

Priority 54/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Android vulnerabilities

Related CVEs

CVE-2010-2245 HIGH 7.4 UPGRADE XML External Entity (XXE) vulnerability in Apache Wink 1.1.1 and earlier allows remote attackers to read arbit

References

← Back to latest CVEs