{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5625 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5625 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-5625 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-5625 in the wild and no public exploit code.\n\nAffected product: Eaton HALO 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-2019-5625/ (Markdown: https://insights.sbomify.com/CVE-2019-5625/index.md)","id":"CVE-2019-5625","markdown":"https://insights.sbomify.com/CVE-2019-5625/index.md","name":"CVE-2019-5625","record":{"aliases":["GHSA-jpj5-3f5g-vc77"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Eaton Halo Home Android App","requires_auth":"low_privilege","summary":"An attacker with physical access or a malicious app can steal OAuth tokens from insecure storage to impersonate users and access their cloud data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"halo_home","vendor":"eaton"}],"cvss":{"score":2.8,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"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.","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":"Eaton Halo Home Android App Insecure Storage","id":"CVE-2019-5625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"BlueCats Reveal Android App Insecure Storage","id":"CVE-2019-5626"},"packages":[],"prev":{"headline":"Rapid7 Metasploit Framework Zip Import Directory Traversal","id":"CVE-2019-5624"},"products":["HALO Home"],"published":"2019-05-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-04","vendors":["Eaton"]},"summary":"An attacker with physical access or a malicious app can steal OAuth tokens from insecure storage to impersonate users and access their cloud data.","url":"https://insights.sbomify.com/CVE-2019-5625/"}