{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5249 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5249 is a critical vulnerability in Wink - Smart Home, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-5249 and fix it if it is affected.\n\nWhat it is: CVE-2017-5249 is a critical vulnerability in Wink - Smart Home, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-5249 in the wild and no public exploit code.\n\nAffected product: Wink - Smart Home. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-5249/ (Markdown: https://insights.sbomify.com/CVE-2017-5249/index.md)","id":"CVE-2017-5249","markdown":"https://insights.sbomify.com/CVE-2017-5249/index.md","name":"CVE-2017-5249","record":{"aliases":["GHSA-vfc9-93vh-4x8h"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart Home Android app","requires_auth":"none","summary":"Attackers can access unencrypted OAuth tokens from the Wink Smart Home Android app, potentially leading to unauthorized account access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"wink","vendor":"wink"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"},{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in Wink - Smart Home","id":"CVE-2017-5249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Insteon for Hub","id":"CVE-2017-5250"},"packages":[],"prev":{"headline":"Cross-site scripting in Secure File Transfer","id":"CVE-2017-5247"},"products":["Wink - Smart Home"],"published":"2018-02-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Wink Labs Inc"]},"summary":"Attackers can access unencrypted OAuth tokens from the Wink Smart Home Android app, potentially leading to unauthorized account access.","url":"https://insights.sbomify.com/CVE-2017-5249/"}