Lucene search
K

8 matches found

RedhatCVE
RedhatCVE
added 2026/01/09 9:35 a.m.6 views

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

7.5CVSS6.7AI score0.00104EPSS
Exploits0References1
OSV
OSV
added 2024/05/08 5:51 p.m.16 views

GO-2024-2818 Consensus failures in github.com/btcsuite/btcd

Incorrect implementation of the consensus rules outlined in BIP 68 and BIP 112 making btcd susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds...

7.5CVSS7.4AI score0.00104EPSS
Exploits0References5
Veracode
Veracode
added 2024/05/07 7:58 a.m.15 views

Race Condition

btcd is vulnerable to a Race Condition. The vulnerability is due to the incorrect implementation of consensus rules as outlined in BIP 68 and BIP 112, specifically by treating the transaction version as a signed integer instead of unsigned. This misinterpretation can lead to a chain split and...

7.5CVSS6.7AI score0.00104EPSS
Exploits0References4Affected Software1
OSV
OSV
added 2024/05/05 3:30 a.m.9 views

GHSA-3JGF-R68H-XFQM btcd susceptible to consensus failures

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

7.5CVSS7.4AI score0.00104EPSS
Exploits0References8
NVD
NVD
added 2024/05/05 1:15 a.m.10 views

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

7.5CVSS6.4AI score0.00104EPSS
Exploits0References3
OSV
OSV
added 2024/05/05 1:15 a.m.2 views

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

7.5CVSS7.4AI score
Exploits0References3
Vulnrichment
Vulnrichment
added 2024/05/05 12:0 a.m.13 views

CVE-2024-34478

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of...

6.7AI score0.00104EPSS
Exploits0References3
CVE
CVE
added 2024/05/05 12:0 a.m.27 views

CVE-2024-34478

CVE-2024-34478 affects btcd before 0.24.0, where the software does not correctly implement BIP 68/BIP 112 consensus rules. The core issue is treating the transaction version as a signed integer instead of unsigned, which can cause consensus failures, potentially leading to a chain split and loss ...

7.5CVSS6.6AI score0.00104EPSS
Exploits0References3Affected Software1
Rows per page
Query Builder