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

Merge pull request #675 from Foundation-Devices/fix/verify-change-before-review

Public commit record

What the developer wrote

Authored by Jacksper13

83/100 · Strong
Merge pull request #675 from Foundation-Devices/fix/verify-change-before-review

Complete change verification before transaction review
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This firmware update moves the verification of Bitcoin 'change' addresses to happen before the user reviews the transaction on screen. Previously, the device checked whether change outputs truly belonged to the wallet only after the user had already approved the transaction and while it was about to sign. Because the review screen hides change outputs from the user, a malicious or buggy PSBT could have asked the device to send change to an attacker's address, and the user would never see it before approving. The fix ensures the wallet proves it owns every hidden change output before showing the review screen, so a mismatch aborts the transaction before the user is asked to confirm.

Recommended action

Treat this as a security-hardening fix with defensive value against PSBT change-address attacks. Users should install the firmware update once released. Developers should verify that no other signing paths bypass the pre-review change check and that the unit tests are run in CI.

Security signals we found

01

Reorders security-critical validation to occur before user approval

02

Validates change-output ownership before the review screen hides those outputs

03

Prevents transaction signing if change derivation does not match the PSBT

04

Closes sensitive key-material context before presenting the review page

05

Adds unit tests covering ownership verification for multiple script types and key mismatch cases

Risk score

Why this scored 71/100

Our methodology →
Potential impact 22/30
Exploitability 16/25
Stealth signal 10/15
Affected reach 12/15
Confidence 7/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.