# CVE-2018-10812: Information disclosure in n/a

> Local attackers with root access can steal digital currency by reading cleartext initial keys stored in application preference files.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8rhq-wwg6-2476

## What is CVE-2018-10812?

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

### Official description

The Bitpie application through 3.2.4 for Android and iOS uses cleartext storage for digital currency initial keys, which allows local users to steal currency by leveraging root access to read /com.biepie/shared_prefs/com.bitpie_preferences.xml (on Android) or a plist file in the app data folder (on iOS).

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2018-10812?

It affects 1 product.


Products: Bitpie Bitcoin Wallet.

## How do I fix CVE-2018-10812?

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

## Is CVE-2018-10812 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10812 and fix it if it is affected.

What it is: CVE-2018-10812 is a medium-severity vulnerability in n/a, published on 8 May 2018. 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-2018-10812 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-2018-10812/ (Markdown: https://insights.sbomify.com/CVE-2018-10812/index.md)
```

## Sources

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

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