AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
High 73 Bitcoin

Merge pull request #662 from Foundation-Devices/fix/unverified-psbt-fees

Public commit record

What the developer wrote

Authored by Jacksper13

58/100 · Thin
Merge pull request #662 from Foundation-Devices/fix/unverified-psbt-fees

Avoid displaying unverified PSBT fees
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This firmware update fixes a security issue in the Passport hardware wallet's handling of Bitcoin transaction fees. Previously, when a transaction file (PSBT) only provided a claimed input amount without the full previous transaction to prove it, Passport would calculate and display a network fee as if it were verified. A malicious or buggy companion wallet could lie about input amounts, making the fee look smaller than it actually is and tricking the user into approving a transaction that sends more money to fees or an attacker than shown. The fix marks such fees as 'Unverified' on screen and in warnings, and adds cross-checks when both witness and non-witness input data are present. It also moves key-derivation verification earlier so bogus ownership metadata cannot be recorded in the device's history cache.

Recommended action

Users should install the firmware release containing this commit. Until updated, treat any displayed network fee in a PSBT with only witness-UTXO inputs as potentially unverified, and verify the total amount being sent independently. Wallet software interacting with Passport should provide full previous transactions (non-witness UTXOs) for inputs when possible so fees can be verified.

Security signals we found

01

UI now displays 'Unverified' instead of a numeric network fee when input amounts cannot be independently verified

02

New assertion prevents witness/non-witness UTXO value or scriptPubKey mismatch for the same input

03

History-cache amount updates are deferred until after cryptographic proof of input ownership is completed

04

Fee percentage and 'Big/Huge Fee' warnings are skipped when the fee is unverified

05

Refactored key-derivation check is applied before signing and before caching, closing a metadata-forgery window

Risk score

Why this scored 73/100

Our methodology →
Potential impact 22/30
Exploitability 16/25
Stealth signal 11/15
Affected reach 12/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.