First published: Wed May 22 2019(Updated: )
The Android mobile application Halo Home before 1.11.0 stores OAuth authentication and refresh access tokens in a clear text file. This file persists until the user logs out of the application and reboots the device. This vulnerability can allow an attacker to impersonate the legitimate user by reusing the stored OAuth token, thus allowing them to view and change the user's personal information stored in the backend cloud service. The attacker would first need to gain physical control of the Android device or compromise it with a malicious app.
Credit: cve@rapid7.con
Affected Software | Affected Version | How to fix |
---|---|---|
Eaton Halo Home | =1.9.0 |
Users should update their HALO Home app to v1.11.0 or higher via Google Play.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-5625 is high with a severity value of 7.1.
CVE-2019-5625 affects the Android mobile application Halo Home before version 1.11.0.
CVE-2019-5625 allows an attacker to impersonate the legitimate user of the Halo Home application.
To fix CVE-2019-5625, update your Halo Home application to version 1.11.0 or later.
More information about CVE-2019-5625 can be found in the following references: [Link 1](https://blog.rapid7.com/2019/05/21/investigating-the-plumbing-of-the-iot-ecosystem-r7-2018-65-r7-2019-07-fixed/), [Link 2](https://www.eaton.com/content/dam/eaton/company/news-insights/cybersecurity/security-bulletins/CVE-2019-5625-Halo-home-smart-lighting-vulnerability-advisory.pdf)