{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31290 exists.","fix":"No fix has been published for CVE-2023-31290 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31290 is a medium-severity vulnerability in n/a, published on 27 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31290 and fix it if it is affected.\n\nWhat it is: CVE-2023-31290 is a medium-severity vulnerability in n/a, published on 27 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31290 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-31290/ (Markdown: https://insights.sbomify.com/CVE-2023-31290/index.md)","id":"CVE-2023-31290","markdown":"https://insights.sbomify.com/CVE-2023-31290/index.md","name":"CVE-2023-31290","record":{"aliases":["GHSA-pm4f-pggw-8jwc"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Trust Wallet Core","requires_auth":"none","summary":"Insufficient entropy in mnemonic generation allows attackers to predict wallet addresses and steal funds from Trust Wallet users.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trust_wallet_browser_extension","vendor":"trustwallet"},{"product":"trust_wallet_core","vendor":"trustwallet"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"Trust Wallet Core before 3.1.1, as used in the Trust Wallet browser extension before 0.0.183, allows theft of funds because the entropy is 32 bits, as exploited in the wild in December 2022 and March 2023. This occurs because the mt19937 Mersenne Twister takes a single 32-bit value as an input seed, resulting in only four billion possible mnemonics. The affected versions of the browser extension are 0.0.172 through 0.0.182. To steal funds efficiently, an attacker can identify all Ethereum addresses created since the 0.0.172 release, and check whether they are Ethereum addresses that could have been created by this extension. To respond to the risk, affected users need to upgrade the product version and also move funds to a new wallet address.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-05-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-05-07T15:02:22Z","kind":"github_poc","ref":"https://github.com/ohexa/py_trustwallet_wasm","stars":0,"title":"(CVE-2023-31290) Trust Wallet Core before 3.1.1, as used in the Trust Wallet browser extension before 0.0.183, allows theft of funds because the entropy is 32 bits, as exploited in the wild in December 2022 and March 2023."}],"tier":"weaponised"},"has_fix":false,"headline":"Weak cryptography in n/a","id":"CVE-2023-31290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Auth bypass in n/a","id":"CVE-2023-31292"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-31289"},"products":["n/a"],"published":"2023-04-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["n/a"]},"summary":"Insufficient entropy in mnemonic generation allows attackers to predict wallet addresses and steal funds from Trust Wallet users.","url":"https://insights.sbomify.com/CVE-2023-31290/"}