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

psbt crash

Public commit record

What the developer wrote

Authored by ww3512687

0/100 · Opaque
psbt crash
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
The short version

What changed, and why it matters

This commit fixes a bug in the Bitcoin PSBT (Partially Signed Bitcoin Transaction) handling code of the Keystone 3 hardware wallet firmware. The bug involved passing the wrong size for the master fingerprint (mfp) buffer to several Rust/C FFI functions. In C, `sizeof(mfp)` where `mfp` is a function parameter of type `uint8_t*` gives the size of a pointer (typically 4 or 8 bytes), not the actual 4-byte array length. The fix adds an explicit `mfpLen` parameter so the correct length (4 bytes) is passed. The commit title 'psbt crash' suggests this mismatch caused crashes when parsing or signing PSBTs. A separate cleanup refactors how public key arrays are prepared to avoid stack-use-after-scope issues.

Recommended action

Users should upgrade to a firmware version containing this commit. Developers should audit all remaining `sizeof(ptr)` patterns in FFI call sites, especially where buffer lengths are passed for sensitive material like master fingerprints, seeds, and keys. Consider adding compile-time or static-analysis checks to catch pointer-versus-array sizeof misuse.

Security signals we found

01

Out-of-bounds read due to sizeof(pointer) being passed as buffer length

02

Incorrect buffer size argument in FFI calls for master fingerprint

03

Potential stack memory disclosure or crash in PSBT parsing/signing/checking

04

Stack-use-after-scope risk in public key array preparation

05

Commit title explicitly says 'psbt crash' indicating stability/security impact

Risk score

Why this scored 59/100

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