Back to Database
Status published
Unknown
CVE-2024-34478
btcd before 0.24.0 does not correctly implement the consensus rules...
Vulnerability Description
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 funds.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2024-34478
Credits & Attribution
No credits recorded in the NVD database.
References
- https://delvingbitcoin.org/t/disclosure-btcd-consensus-bugs-due-to-usage-of-signed-transaction-version/455
- https://github.com/btcsuite/btcd/blob/e4c88c3a3ecb1813529bf3dddc7a865bd418a6b8/blockchain/chain.go#L383C1-L392C3
- https://github.com/btcsuite/btcd/blob/e4c88c3a3ecb1813529bf3dddc7a865bd418a6b8/txscript/opcode.go#L1172C1-L1178C3
More from n/a
View All →CVE-2025-9910
Versions of the package jsondiffpatch before 0.7.2 are vulnerable to...
Low
2.3
CVE-2025-9802
RemoteClinic profile.php sql injection
Medium
5.1
CVE-2025-9799
Langfuse Webhook promptRouter.ts promptChangeEventSourcing server-side request forgery
Low
2.3
CVE-2025-9775
RemoteClinic edit-my-profile.php unrestricted upload
Medium
6.9
CVE-2025-9774
RemoteClinic edit-patient.php information disclosure
Medium
5.3
Affected Vendor
Affected Software
Unknown
Vulnerable Versions:
Unknown
Timeline
Official Publish:
May 5th, 2024
Last Modified:
August 7th, 2024
Added to House:
July 22nd, 2026
CVSS Vectors
No vector data available
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.