Lucene search
+L

9 matches found

RedhatCVE
RedhatCVE
•added 2026/01/09 9:35 a.m.•19 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.00558EPSS
SaveExploits0References1
OSV
OSV
•added 2024/05/08 5:51 p.m.•28 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.4AI score0.00558EPSS
SaveExploits0References5
Veracode
Veracode
•added 2024/05/07 7:58 a.m.•25 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.00558EPSS
SaveExploits0References4Affected Software1
OSV
OSV
•added 2024/05/05 3:30 a.m.•27 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.4AI score0.00558EPSS
SaveExploits0References8
NVD
NVD
•added 2024/05/05 1:15 a.m.•26 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.00558EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
•added 2024/05/05 12:00 a.m.•17 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.00558EPSS
SaveExploits0References3
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/05/05 12:00 a.m.•5 views

CVE-2024-34478: Interpretation Conflict

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.5CVSS5.8AI score0.00558EPSS
SaveExploits0References1
CVE
CVE
•added 2024/05/05 12:00 a.m.•57 views

CVE-2024-34478

The btcd Bitcoin implementation (prior to version 0.24.0 ) contains a consensus failure vulnerability due to an incorrect implementation of BIP 68 and BIP 112 rules. The software incorrectly treats the transaction version as a signed integer instead of an unsigned integer. This discrepancy in con...

6.6AI score0.00558EPSS
SaveExploits0References3Affected Software1
OSV
OSV
•added 2024/05/05 12:00 a.m.•18 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
SaveExploits0References5
Rows per page
Query Builder