# CVE-2021-36689: Weak cryptography in n/a

> Attackers can decrypt sensitive wallet data by brute-forcing the short PIN if they possess the recovered data file.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 3 Mar 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-j77q-57r3-74g7

## What is CVE-2021-36689?

CVE-2021-36689 is a medium-severity vulnerability in n/a, published on 3 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue discovered in com.samourai.wallet.PinEntryActivity.java in Streetside Samourai Wallet 0.99.96i allows attackers to view sensitive information and decrypt data via a brute force attack that uses a recovered samourai.dat file. The PIN is 5 to 8 digits, which may be insufficient in this situation.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2021-36689?

It affects 1 product.


Products: Samourai-Wallet-Android Project Samourai-Wallet-Android.

## How do I fix CVE-2021-36689?

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

## Is CVE-2021-36689 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36689 and fix it if it is affected.

What it is: CVE-2021-36689 is a medium-severity vulnerability in n/a, published on 3 Mar 2023. 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-2021-36689 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-2021-36689/ (Markdown: https://insights.sbomify.com/CVE-2021-36689/index.md)
```

## Sources

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

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