Pending transaction replacement via reused UTXOs
Published Jul 30, 2024 · Updated Aug 2, 2024
Improper input validation in Fuel Labs Fuel TypeScript SDK before 0.93.0 allows remote authenticated users to replace pending transactions. The Account.fund function calls getResourcesToSpend statelessly and fails to exclude UTXOs already assigned to other transactions in the same block. Funding multiple transactions before block production can reuse a randomly selected UTXO, causing a new submission to fail or evict the earlier transaction from the transaction pool.
Summary
What happened
Improper input validation in Fuel Labs Fuel TypeScript SDK before 0.93.0 allows remote authenticated users to replace pending transactions. The Account.fund function calls getResourcesToSpend statelessly and fails to exclude UTXOs already assigned to other transactions in the same block. Funding multiple transactions before block production can reuse a randomly selected UTXO, causing a new submission to fail or evict the earlier transaction from the transaction pool.
The record
- CVE
- CVE-2024-41945
- Published
- Jul 30, 2024
- Updated
- Aug 2, 2024
- Vendor
- Fuel Labs
- Product
- Fuel TypeScript SDK
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <0.93.0
- Affected versionversion=< 0.93.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
Public exploit references
- Upstream concurrent-transaction proof of conceptproof of concept · demonstrated
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