# CVE-2024-23660: Weak cryptography in n/a

> Insufficient entropy in mnemonic generation allows attackers to predict wallet keys and steal funds from Binance Trust Wallet iOS users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 15 May 2025
- **Also known as:** GHSA-hcm7-vvxh-5crx

## What is CVE-2024-23660?

CVE-2024-23660 is a high-severity vulnerability in n/a, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Binance Trust Wallet app for iOS in commit 3cd6e8f647fbba8b5d8844fcd144365a086b629f, git tag 0.0.4 misuses the trezor-crypto library and consequently generates mnemonic words for which the device time is the only entropy source, leading to economic losses, as exploited in the wild in July 2023. An attacker can systematically generate mnemonics for each timestamp within an applicable timeframe, and link them to specific wallet addresses in order to steal funds from those wallets.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2024-23660?

It affects 1 product.


Products: Binance Trust Wallet.

## How do I fix CVE-2024-23660?

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

## Is CVE-2024-23660 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23660 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23660 and fix it if it is affected.

What it is: CVE-2024-23660 is a high-severity vulnerability in n/a, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23660 exists.

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-2024-23660/ (Markdown: https://insights.sbomify.com/CVE-2024-23660/index.md)
```

## Sources

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

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