# CVE-2019-5626: BlueCats Reveal Android App Insecure Storage

> An attacker with physical access or a malicious app can read stored credentials from the BlueCats Reveal Android app, potentially compromising the network.

- **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-w7p8-rgxr-jhj7

## What is CVE-2019-5626?

CVE-2019-5626 is a low-severity vulnerability in BlueCats Reveal, 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 BlueCats Reveal before 3.0.19 stores the username and password in a clear text file. This file persists until the user logs out or the session times out from non-usage (30 days of no user activity). This can allow an attacker to compromise the affected BlueCats network implementation. 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-5626?

It affects 1 product.


Products: Bluecats Bluecats Reveal.

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

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

## Is CVE-2019-5626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5626 is a low-severity vulnerability in BlueCats Reveal, 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-5626 in the wild and no public exploit code.

Affected product: BlueCats Reveal. 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-5626/ (Markdown: https://insights.sbomify.com/CVE-2019-5626/index.md)
```

## Sources

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

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