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

fix multisig

Public commit record

What the developer wrote

Authored by ww3512687

18/100 · Opaque
fix multisig
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a Bitcoin multisig signing flow in the Keystone 3 hardware wallet firmware. Previously, when a transaction did not need a signature, the code exported the PSBT but did not properly handle the result object; when it did need a signature, it signed but skipped updating the UI status and freeing the result. The patch unifies both branches so the result is always processed and cleaned up. It also wraps some legacy Keystone transaction code in a WEB3_VERSION compile guard, likely preventing it from running on Bitcoin-only firmware builds where it could behave incorrectly.

Recommended action

Review the ownership semantics of UREncodeResult inside MultisigSignResult to confirm the unified free path is safe. Verify that WEB3_VERSION is correctly defined for the intended product variants and that excluding these legacy paths does not break other supported workflows. Consider adding regression tests for both export-only and signing multisig flows.

Security signals we found

01

Memory-management asymmetry in multisig signing path (possible leak or use-after-free depending on btc_sign_multisig_psbt ownership)

02

Missing UI status update in the signing branch of BtcSignPsbtMultisig

03

Legacy UTXO code paths executed unconditionally despite BTC_ONLY build, now gated by WEB3_VERSION

04

Potential NULL/undefined behavior from xPub/hdPath on BTC_ONLY builds before the guard

Risk score

Why this scored 42/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 6/15
Affected reach 7/15
Confidence 6/10
Evidence quality 3/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.