Upstream information
Description
btcd is an alternative full node bitcoin implementation written in Go (golang). The btcd Bitcoin client (versions 0.10 to 0.24) did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality. This logic is consensus-critical: the difference in behavior with the other Bitcoin clients can lead to btcd clients accepting an invalid Bitcoin block (or rejecting a valid one). This consensus failure can be leveraged to cause a chain split (accepting an invalid Bitcoin block) or be exploited to DoS the btcd nodes (rejecting a valid Bitcoin block). An attacker can create a standard transaction where FindAndDelete doesn't return a match but removeOpCodeByData does making btcd get a different sighash, leading to a chain split. Importantly, this vulnerability can be exploited remotely by any Bitcoin user and does not require any hash power. This is because the difference in behavior can be triggered by a "standard" Bitcoin transaction, that is a transaction which gets relayed through the P2P network before it gets included in a Bitcoin block. `removeOpcodeByData(script []byte, dataToRemove []byte)` removes any data pushes from `script` that contain `dataToRemove`. However, `FindAndDelete` only removes exact matches. So for example, with `script = "<data> <data||foo>"` and `dataToRemove = "data"` btcd will remove both data pushes but Bitcoin Core's `FindAndDelete` only removes the first `<data>` push. This has been patched in btcd version v0.24.2. Users are advised to upgrade. There are no known workarounds for this issue.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having important severity.
| CNA (GitHub) | |
|---|---|
| Base Score | 7.4 |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H |
| Attack Vector | Network |
| Attack Complexity | High |
| Privileges Required | None |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | None |
| Integrity Impact | High |
| Availability Impact | High |
| CVSSv3 Version | 3.1 |
SUSE Security Advisories:
- SUSE-SU-2024:3911-1, published 2024-11-05T07:45:06Z
- openSUSE-SU-2024:0350-1, published Tue Nov 5 22:50:01 2024
- openSUSE-SU-2024:14447-1, published Sat Nov 2 18:49:02 2024
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| SUSE Linux Enterprise Module for Package Hub 15 SP5 |
| Patchnames: SUSE-SLE-Module-Packagehub-Subpackages-15-SP5-2024-3911 |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 |
| Patchnames: SUSE-SLE-Module-Packagehub-Subpackages-15-SP6-2024-3911 |
| SUSE Package Hub 12 |
| Patchnames: openSUSE-2024-350 |
| openSUSE Leap 15.5 |
| Patchnames: openSUSE-SLE-15.5-2024-3911 |
| openSUSE Leap 15.6 |
| Patchnames: openSUSE-SLE-15.6-2024-3911 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2024-14447 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | govulncheck-vulndb | Released |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | Released |
| openSUSE Leap 15.5 | govulncheck-vulndb | Released |
| openSUSE Leap 15.6 | govulncheck-vulndb | Released |
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE Package Hub 12 | govulncheck-vulndb | Released |
SUSE Timeline for this CVE
CVE page created: Sat Oct 12 00:00:26 2024CVE page last modified: Wed Nov 6 00:54:03 2024