DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2024-38365. Reason: This record is a duplicate of CVE-2024-38365. Notes: All CVE users should reference CVE-2024-38365 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage.
Metrics
Affected Vendors & Products
No data.
No data.
No data.
No data.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
No reference.
History
Fri, 11 Oct 2024 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 11 Oct 2024 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In btcd before 0.24.2, removeOpcodeByData mishandles the consensus rules for legacy signature verification. There can be a standard transaction that would be considered valid by Bitcoin Core but invalid by btcd. | DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2024-38365. Reason: This record is a duplicate of CVE-2024-38365. Notes: All CVE users should reference CVE-2024-38365 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
Thu, 10 Oct 2024 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In btcd before 0.24.2, removeOpcodeByData mishandles the consensus rules for legacy signature verification. There can be a standard transaction that would be considered valid by Bitcoin Core but invalid by btcd. | |
| References |
|
MITRE
Status: REJECTED
Assigner: mitre
Published:
Updated: 2024-10-11T20:26:22.924642
Reserved: 2024-05-18T00:00:00
Link: CVE-2024-36051
Vulnrichment
Updated:
NVD
Status : Rejected
Published: 2024-10-10T13:15:14.187
Modified: 2024-10-11T21:15:06.843
Link: CVE-2024-36051
Redhat
No data.
OpenCVE Enrichment
No data.