Oversized tapscript relay via absent policy limit
Published Apr 30, 2024 · Updated Nov 21, 2024
Improper input validation in Bitcoin Core through 27.0 allows remote attackers to relay oversized tapscripts without a proposed policy limit. IsWitnessStandard applies a script-size check to P2WSH but not to a Taproot script-path witness; the proposed patch would add the same check there. Reachability requires a valid Taproot transaction, and maintainers dispute the vulnerability because transaction and block weight rules already bound resource use.
Summary
What happened
Improper input validation in Bitcoin Core through 27.0 allows remote attackers to relay oversized tapscripts without a proposed policy limit. IsWitnessStandard applies a script-size check to P2WSH but not to a Taproot script-path witness; the proposed patch would add the same check there. Reachability requires a valid Taproot transaction, and maintainers dispute the vulnerability because transaction and block weight rules already bound resource use.
The record
- CVE
- CVE-2024-34149
- Published
- Apr 30, 2024
- Updated
- Nov 21, 2024
- Vendor
- Bitcoin Core
- Product
- Bitcoin Core
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo