# CVE-2019-8350: Information disclosure in n/a

> An Android banking app leaked user passwords to keyboard autocomplete caches, allowing third-party keyboards to store or transmit credentials in cleartext.

- **Severity:** Medium 6.6 (`CVSS:3.0/AC:L/AV:P/A:H/C:H/I:H/PR:L/S:U/UI: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:** 13 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mjp6-fq4v-qgrp

## What is CVE-2019-8350?

CVE-2019-8350 is a medium-severity vulnerability in n/a, published on 13 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Simple - Better Banking application 2.45.0 through 2.45.3 (fixed in 2.46.0) for Android was affected by an information disclosure vulnerability that leaked the user's password to the keyboard autocomplete functionality. Third-party Android keyboards that capture the password may store this password in cleartext, or transmit the password to third-party services for keyboard customization purposes. A compromise of any datastore that contains keyboard autocompletion caches would result in the disclosure of the user's Simple Bank password.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Simple Better Banking.

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

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

## Is CVE-2019-8350 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8350 is a medium-severity vulnerability in n/a, published on 13 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-8350 in the wild and no public exploit code.

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

## Sources

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

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