{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-40769 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-40769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-40769 is a high-severity vulnerability in n/a, published on 18 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-40769 and fix it if it is affected.\n\nWhat it is: CVE-2022-40769 is a high-severity vulnerability in n/a, published on 18 Sep 2022. 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-2022-40769 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-2022-40769/ (Markdown: https://insights.sbomify.com/CVE-2022-40769/index.md)","id":"CVE-2022-40769","markdown":"https://insights.sbomify.com/CVE-2022-40769/index.md","name":"CVE-2022-40769","record":{"aliases":["GHSA-9q2f-7hm7-62h6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethereum vanity address tool","requires_auth":"none","summary":"Attackers can recover private keys from Ethereum vanity addresses due to weak RNG initialization, allowing theft of cryptocurrency.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"profanity","vendor":"profanity_project"}],"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":"profanity through 1.60 has only four billion possible RNG initializations. Thus, attackers can recover private keys from Ethereum vanity addresses and steal cryptocurrency, as exploited in the wild in June 2022.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-01-28","github_poc":2,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-01-28T00:12:31Z","kind":"github_poc","ref":"https://github.com/PLSRcoin/CVE-2022-40769","stars":1,"title":"profanity through 1.60 has only four billion possible RNG initializations. Thus, attackers can recover private keys from Ethereum vanity addresses and steal cryptocurrency, as exploited in the wild in June 2022. CVE project by @Sn0wAlice"},{"date":"2026-09-23T22:09:27Z","kind":"github_poc","ref":"https://github.com/artsbykriss/profanity-verifier","stars":0,"title":"Provable check for CVE-2022-40769: does an EOA's private key lie in the Profanity-reachable key space?"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Weak cryptography in n/a","id":"CVE-2022-40769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2022-40770"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-40768"},"products":["n/a"],"published":"2022-09-18","related":[{"cvss_score":5.9,"headline":"Other in n/a","id":"CVE-2017-5592","kev_date_added":null,"published":"2017-02-09"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can recover private keys from Ethereum vanity addresses due to weak RNG initialization, allowing theft of cryptocurrency.","url":"https://insights.sbomify.com/CVE-2022-40769/"}