Vulnerability-Lookup

CNVD-2021-38774

Vulnerability from cnvd - Published: 2021-06-02

Title

Bitcoin Core存在未明漏洞（CNVD-2021-38774）

Description

Bitcoin Core是一款用于验证区块链交易有效性的开源客户端。 Bitcoin Core存在安全漏洞，该漏洞允许远程攻击者可利用该漏洞绕过某些安全限制。

Severity

中

Patch Name

Bitcoin Core存在未明漏洞（CNVD-2021-38774）的补丁

Patch Description

Bitcoin Core是一款用于验证区块链交易有效性的开源客户端。 Bitcoin Core存在安全漏洞，该漏洞允许远程攻击者可利用该漏洞绕过某些安全限制。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876

Reference

https://www.cybersecurity-help.cz/vdb/SB2021050703

Impacted products

Name
Bitcoin Bitcoin Core >=0.12.0，<=0.21.1

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-31876"
    }
  },
  "description": "Bitcoin Core\u662f\u4e00\u6b3e\u7528\u4e8e\u9a8c\u8bc1\u533a\u5757\u94fe\u4ea4\u6613\u6709\u6548\u6027\u7684\u5f00\u6e90\u5ba2\u6237\u7aef\u3002\n\nBitcoin Core\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u5141\u8bb8\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u67d0\u4e9b\u5b89\u5168\u9650\u5236\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2021-38774",
  "openTime": "2021-06-02",
  "patchDescription": "Bitcoin Core\u662f\u4e00\u6b3e\u7528\u4e8e\u9a8c\u8bc1\u533a\u5757\u94fe\u4ea4\u6613\u6709\u6548\u6027\u7684\u5f00\u6e90\u5ba2\u6237\u7aef\u3002\r\n\r\nBitcoin Core\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u5141\u8bb8\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u67d0\u4e9b\u5b89\u5168\u9650\u5236\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Bitcoin Core\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\uff08CNVD-2021-38774\uff09\u7684\u8865\u4e01",
  "products": {
    "product": "Bitcoin Bitcoin Core \u003e=0.12.0\uff0c\u003c=0.21.1"
  },
  "referenceLink": "https://www.cybersecurity-help.cz/vdb/SB2021050703",
  "serverity": "\u4e2d",
  "submitTime": "2021-05-11",
  "title": "Bitcoin Core\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\uff08CNVD-2021-38774\uff09"
}

CVE-2021-31876 (GCVE-0-2021-31876)

Vulnerability from cvelistv5 – Published: 2021-05-13 21:03 – Updated: 2024-08-03 23:10

Summary

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 <= 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.

Severity

No CVSS data available.

CWE

Assigner

mitre CNA under the mitre root

CNA scorecard E 29/100 over 2193 records in the last 180 days details

References

5 references

URL	Tags
https://en.bitcoin.it/wiki/Common_Vulnerabilities…	x_refsource_MISC
https://bitcoinops.org/en/topics/replace-by-fee/	x_refsource_MISC
https://github.com/bitcoin/bitcoin	x_refsource_MISC
https://lists.linuxfoundation.org/pipermail/bitco…	x_refsource_MISC
https://bitcoinops.org/en/newsletters/2021/05/12/	x_refsource_MISC

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T23:10:31.041Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://bitcoinops.org/en/topics/replace-by-fee/"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/bitcoin/bitcoin"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://bitcoinops.org/en/newsletters/2021/05/12/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2021-05-13T21:03:38.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://bitcoinops.org/en/topics/replace-by-fee/"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/bitcoin/bitcoin"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://bitcoinops.org/en/newsletters/2021/05/12/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2021-31876",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876",
              "refsource": "MISC",
              "url": "https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876"
            },
            {
              "name": "https://bitcoinops.org/en/topics/replace-by-fee/",
              "refsource": "MISC",
              "url": "https://bitcoinops.org/en/topics/replace-by-fee/"
            },
            {
              "name": "https://github.com/bitcoin/bitcoin",
              "refsource": "MISC",
              "url": "https://github.com/bitcoin/bitcoin"
            },
            {
              "name": "https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html",
              "refsource": "MISC",
              "url": "https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html"
            },
            {
              "name": "https://bitcoinops.org/en/newsletters/2021/05/12/",
              "refsource": "MISC",
              "url": "https://bitcoinops.org/en/newsletters/2021/05/12/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2021-31876",
    "datePublished": "2021-05-13T21:03:38.000Z",
    "dateReserved": "2021-04-29T00:00:00.000Z",
    "dateUpdated": "2024-08-03T23:10:31.041Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted