Excessive transaction fees via recombined Segwit signatures
Published Jun 16, 2020 · Updated Aug 4, 2024
Improper signature verification in BIP-143 hardware wallets allows remote attackers to induce excessive Bitcoin transaction fees. BIP-143 binds each Segwit input amount only to its own signature, allowing signatures from two user-approved transactions to be recombined into a third transaction with larger real inputs. Malicious wallet software must control the proposed transactions and persuade the user to confirm two apparently identical requests, after which the recombined transaction can consume the difference as a fee.
Summary
What happened
Improper signature verification in BIP-143 hardware wallets allows remote attackers to induce excessive Bitcoin transaction fees. BIP-143 binds each Segwit input amount only to its own signature, allowing signatures from two user-approved transactions to be recombined into a third transaction with larger real inputs. Malicious wallet software must control the proposed transactions and persuade the user to confirm two apparently identical requests, after which the recombined transaction can consume the difference as a fee.
The record
- CVE
- CVE-2020-14199
- Published
- Jun 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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