Filtered by vendor Bitcoin
Subscriptions
Filtered by product Bitcoin Core
Subscriptions
Total
50 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-37192 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-20 | 7.5 High |
| Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory, potentially allowing them to redirect Bitcoin transactions to wallets of their own choosing. | ||||
| CVE-2024-52922 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 6.5 Medium |
| 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. | ||||
| CVE-2019-25220 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| 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. | ||||
| CVE-2015-20111 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 9.8 Critical |
| miniupnp before 4c90b87, as used in Bitcoin Core before 0.12 and other products, lacks checks for snprintf return values, leading to a buffer overflow and significant data leak, a different vulnerability than CVE-2019-12107. In Bitcoin Core before 0.12, remote code execution was possible in conjunction with CVE-2015-6031 exploitation. | ||||
| CVE-2024-52919 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 6.5 Medium |
| Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages. | ||||
| CVE-2024-52918 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 6.5 Medium |
| Bitcoin-Qt in Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption and application crash) via a BIP21 r parameter for a URL that has a large file. | ||||
| CVE-2024-52920 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (infinite loop) via a malformed GETDATA message. | ||||
| CVE-2024-52912 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an abs64 logic bug. | ||||
| CVE-2024-52917 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 6.5 Medium |
| Bitcoin Core before 22.0 has a miniupnp infinite loop in which it allocates memory on the basis of random data received over the network, e.g., large M-SEARCH replies from a fake UPnP device. | ||||
| CVE-2024-52916 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers. | ||||
| CVE-2024-52921 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 5.3 Medium |
| In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block. | ||||
| CVE-2024-52915 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message. | ||||
| CVE-2024-52914 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 7.5 High |
| In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. | ||||
| CVE-2024-52913 | 1 Bitcoin | 1 Bitcoin Core | 2024-11-18 | 5.3 Medium |
| In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled. | ||||
| CVE-2010-5140 | 1 Bitcoin | 2 Bitcoin Core, Wxbitcoin | 2024-09-17 | N/A |
| wxBitcoin and bitcoind before 0.3.13 do not properly handle bitcoins associated with Bitcoin transactions that have zero confirmations, which allows remote attackers to cause a denial of service (invalid-transaction flood) by sending low-valued transactions without transaction fees. | ||||
| CVE-2012-4683 | 1 Bitcoin | 1 Bitcoin Core | 2024-09-17 | N/A |
| Unspecified vulnerability in bitcoind and Bitcoin-Qt allows attackers to cause a denial of service via unknown vectors, a different vulnerability than CVE-2012-4682. | ||||
| CVE-2010-5138 | 1 Bitcoin | 2 Bitcoin Core, Wxbitcoin | 2024-09-17 | N/A |
| wxBitcoin and bitcoind 0.3.x allow remote attackers to cause a denial of service (electricity consumption) via a Bitcoin transaction containing multiple OP_CHECKSIG script opcodes. | ||||
| CVE-2012-4682 | 1 Bitcoin | 1 Bitcoin Core | 2024-09-17 | N/A |
| Unspecified vulnerability in bitcoind and Bitcoin-Qt allows attackers to cause a denial of service via unknown vectors, a different vulnerability than CVE-2012-4683. | ||||
| CVE-2011-4447 | 1 Bitcoin | 2 Bitcoin Core, Wxbitcoin | 2024-09-17 | N/A |
| The "encrypt wallet" feature in wxBitcoin and bitcoind 0.4.x before 0.4.1, and 0.5.0rc, does not properly interact with the deletion functionality of BSDDB, which allows context-dependent attackers to obtain unencrypted private keys from Bitcoin wallet files by bypassing the BSDDB interface and reading entries that are marked for deletion. | ||||
| CVE-2012-3789 | 1 Bitcoin | 1 Bitcoin Core | 2024-09-17 | N/A |
| Unspecified vulnerability in bitcoind and Bitcoin-Qt before 0.4.7rc3, 0.5.x before 0.5.6rc3, 0.6.0.x before 0.6.0.9rc1, and 0.6.x before 0.6.3rc1 allows remote attackers to cause a denial of service (process hang) via unknown behavior on a Bitcoin network. | ||||