{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-31876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-31876 is a medium-severity vulnerability in n/a, published on 13 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-31876 and fix it if it is affected.\n\nWhat it is: CVE-2021-31876 is a medium-severity vulnerability in n/a, published on 13 May 2021. 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-2021-31876 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-2021-31876/ (Markdown: https://insights.sbomify.com/CVE-2021-31876/index.md)","id":"CVE-2021-31876","markdown":"https://insights.sbomify.com/CVE-2021-31876/index.md","name":"CVE-2021-31876","record":{"aliases":["GHSA-cm2c-8c7c-974f"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin Core client","requires_auth":"none","summary":"Bitcoin Core fails to enforce BIP125 replacement rules, allowing attackers to cause denial of service or loss of funds in downstream projects.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin","vendor":"bitcoin"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with nSequence = 0xff_ff_ff_ff, spending an unconfirmed parent with nSequence \u003c= 0xff_ff_ff_fd, should be replaceable because there is inherited signaling by the child transaction. However, the actual PreChecks implementation does not enforce this. Instead, mempool rejects the replacement attempt of the unconfirmed child transaction.","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":"Business logic in n/a","id":"CVE-2021-31876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2021"},"n_packages":0,"n_references":5,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-31877"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-31875"},"products":["n/a"],"published":"2021-05-13","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-3401","kev_date_added":null,"published":"2021-02-04"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2017-9230","kev_date_added":null,"published":"2017-05-24"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Bitcoin Core fails to enforce BIP125 replacement rules, allowing attackers to cause denial of service or loss of funds in downstream projects.","url":"https://insights.sbomify.com/CVE-2021-31876/"}