{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-52922 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-52922 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-52922 is a medium-severity denial of service vulnerability in Bitcoin Bitcoin Core, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52922 and fix it if it is affected.\n\nWhat it is: CVE-2024-52922 is a medium-severity denial of service vulnerability in Bitcoin Bitcoin Core, published on 18 Nov 2024. 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-2024-52922 in the wild and no public exploit code.\n\nAffected product: Bitcoin Bitcoin Core. 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-2024-52922/ (Markdown: https://insights.sbomify.com/CVE-2024-52922/index.md)","id":"CVE-2024-52922","markdown":"https://insights.sbomify.com/CVE-2024-52922/index.md","name":"CVE-2024-52922","record":{"aliases":["GHSA-3fvw-4j76-wpj7"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin Core node","requires_auth":"none","summary":"An attacker can cause a Bitcoin Core node to delay downloading the latest block by stalling peer communications, leading to a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin_core","vendor":"bitcoin"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"In Bitcoin Core before 25.1, an attacker can cause a node to not download the latest block, because there can be minutes of delay when an announcing peer stalls instead of complying with the peer-to-peer protocol specification.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2024-52922","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"bitcoin:bitcoin_core","products":["bitcoin:bitcoin_core"],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-52923"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2024-52921"},"products":["n/a"],"published":"2024-11-18","related":[{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2025-46597","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-54604","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-54605","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-25220","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2024-52912","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-52914","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-52915","kev_date_added":null,"published":"2024-11-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["n/a"]},"summary":"An attacker can cause a Bitcoin Core node to delay downloading the latest block by stalling peer communications, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2024-52922/"}