{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25220 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-25220 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25220 is a high-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-2019-25220 and fix it if it is affected.\n\nWhat it is: CVE-2019-25220 is a high-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-2019-25220 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-2019-25220/ (Markdown: https://insights.sbomify.com/CVE-2019-25220/index.md)","id":"CVE-2019-25220","markdown":"https://insights.sbomify.com/CVE-2019-25220/index.md","name":"CVE-2019-25220","record":{"aliases":["GHSA-px5f-j76h-8w39"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin Core","requires_auth":"none","summary":"Remote attackers can crash Bitcoin Core nodes by flooding them with low-difficulty header chains, causing 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":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Bitcoin Core before 24.0.1 allows remote attackers to cause a denial of service (daemon crash) via a flood of low-difficulty header chains (aka a \"Chain Width Expansion\" attack) because a node does not first verify that a presented chain has enough work before committing to store it.","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-2019-25220","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"bitcoin:bitcoin_core","products":["bitcoin:bitcoin_core"],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Responsive Filterable Portfolio \u003c=1.0.8 - Authenticated (Admin+) SQL Injection","id":"CVE-2019-25221"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-25219"},"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":"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Remote attackers can crash Bitcoin Core nodes by flooding them with low-difficulty header chains, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2019-25220/"}