{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39910 is a high-severity vulnerability in n/a, published on 9 Aug 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-39910 and fix it if it is affected.\n\nWhat it is: CVE-2023-39910 is a high-severity vulnerability in n/a, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-39910 in the wild and no public exploit code.\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-39910/ (Markdown: https://insights.sbomify.com/CVE-2023-39910/index.md)","id":"CVE-2023-39910","markdown":"https://insights.sbomify.com/CVE-2023-39910/index.md","name":"CVE-2023-39910","record":{"aliases":["GHSA-prgj-h7jq-7p9h"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Libbitcoin Explorer","requires_auth":"none","summary":"Weak entropy in Libbitcoin Explorer allows attackers to recover private keys and steal cryptocurrency funds from affected wallets.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libbitcoin_explorer","vendor":"libbitcoin"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"The cryptocurrency wallet entropy seeding mechanism used in Libbitcoin Explorer 3.0.0 through 3.6.0 is weak, aka the Milk Sad issue. The use of an mt19937 Mersenne Twister PRNG restricts the internal entropy to 32 bits regardless of settings. This allows remote attackers to recover any wallet private keys generated from \"bx seed\" entropy output and steal funds. (Affected users need to move funds to a secure new cryptocurrency wallet.) NOTE: the vendor's position is that there was sufficient documentation advising against \"bx seed\" but others disagree. NOTE: this was exploited in the wild in June and July 2023.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-06-03","github_poc":3,"max_poc_stars":11,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-03T09:00:35Z","kind":"github_poc","ref":"https://github.com/z1ph1us/MilkSad-Mnemonic-Generator","stars":11,"title":"This tool generates BIP-39 mnemonic phrases derived from Unix timestamps, exploring the 'Milk Sad' vulnerability's implications (CVE-2023-39910)"},{"date":"2026-02-07T16:43:51Z","kind":"github_poc","ref":"https://github.com/demining/RAMnesia-Attack","stars":1,"title":"RAMnesia Attack: A Scientific Investigation of WireTap Threats to Bitcoin Infrastructure, Hardware Vulnerabilities (CVE-2025-6202, CVE-2023-39910), and Cryptanalytic Methods for ECDSA Key Recovery"},{"date":"2026-07-31T07:29:32Z","kind":"github_poc","ref":"https://github.com/Xaxis/bitcoin-security","stars":0,"title":"Educational study of Bitcoin key entropy: weak-RNG wallet enumeration (Milk Sad / CVE-2023-39910 class) vs. the infeasibility of brute-forcing a good key."}],"tier":"poc_unverified"},"has_fix":false,"headline":"Weak cryptography in n/a","id":"CVE-2023-39910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"Path traversal in n/a","id":"CVE-2023-39912"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2023-39909"},"products":["n/a"],"published":"2023-08-09","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["n/a"]},"summary":"Weak entropy in Libbitcoin Explorer allows attackers to recover private keys and steal cryptocurrency funds from affected wallets.","url":"https://insights.sbomify.com/CVE-2023-39910/"}