An attacker capable of mining a block with sufficient proof-of-work could have exploited this to crash victim nodes. Because of the nature of use-after-free bugs, it is possible that the crash could have been used for remote code execution, though constraints on the input (block) data make this unlikely.
A new release candidate of Bitcoin Core, v31.0rc4, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDcAt
Binaries are available here: https://t.co/tJBrlaSGYx
A new release candidate of Bitcoin Core, v31.0rc4, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDcAt
Binaries are available here: https://t.co/tJBrlaSGYx
A new release candidate of Bitcoin Core, v31.0rc2, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDcAt
Binaries are available here: https://t.co/cMS1a1uo4v
A new release candidate of Bitcoin Core, v31.0rc2, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDcAt
Binaries are available here: https://t.co/cMS1a1uo4v
A new release candidate of Bitcoin Core, v31.0rc1, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDKq1
Binaries are available here: https://t.co/5yrfcKk6ri
A new release candidate of Bitcoin Core, v31.0rc1, is available for testing.
This is a new major release, and follows v30.2.
Work-in-progress release notes are here: https://t.co/aSo2yLDKq1
Binaries are available here: https://t.co/5yrfcKk6ri
A new release candidate of Bitcoin Core, v30.2rc1, is available for testing.
This is a new minor release, and follows v30.1.
Release notes: https://t.co/nYoQiXWl7u
Binaries are available here: https://t.co/EluQRsFbGi.
NOTICE: Wallet Migration bug present in Bitcoin Core wallet 30.0 & 30.1.
Under rare circumstances, migrating a legacy (BDB) wallet can delete all wallet files on the same node. If those wallets aren’t backed up, this can result in a loss of funds.
A fix will become available in Bitcoin Core 30.2. Until that is released, do not migrate legacy wallets using 30.0 or 30.1.
Only the legacy wallet migration process is affected. All other uses are unaffected. You can continue using Bitcoin Core normally, including existing wallets and running a node without wallets.
NOTICE: Wallet Migration bug present in Bitcoin Core wallet 30.0 & 30.1.
Under rare circumstances, migrating a legacy (BDB) wallet can delete all wallet files on the same node. If those wallets aren’t backed up, this can result in a loss of funds.
A fix will become available in Bitcoin Core 30.2. Until that is released, do not migrate legacy wallets using 30.0 or 30.1.
Only the legacy wallet migration process is affected. All other uses are unaffected. You can continue using Bitcoin Core normally, including existing wallets and running a node without wallets.