# CVE-2019-5625: Eaton Halo Home Android App Insecure Storage

> An attacker with physical access or a malicious app can steal OAuth tokens from insecure storage to impersonate users and access their cloud data.

- **Severity:** Low 2.8 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jpj5-3f5g-vc77

## What is CVE-2019-5625?

CVE-2019-5625 is a low-severity vulnerability in Eaton HALO Home, published on 22 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2019-5625?

It affects 1 product.


Products: Eaton Halo Home.

## How do I fix CVE-2019-5625?

No fix has been published for CVE-2019-5625 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5625 being exploited?

There is no known exploitation of CVE-2019-5625 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5625 and fix it if it is affected.

What it is: CVE-2019-5625 is a low-severity vulnerability in Eaton HALO Home, published on 22 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5625 in the wild and no public exploit code.

Affected product: Eaton HALO Home. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-5625/ (Markdown: https://insights.sbomify.com/CVE-2019-5625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5625
- OSV: https://osv.dev/vulnerability/CVE-2019-5625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-5625/
Summaries are generated and may contain mistakes; the official description above is the record.