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

mnemonic: restore recovery phrase by word number

Public commit record

What the developer wrote

Authored by roderico

68/100 · Adequate
mnemonic: restore recovery phrase by word number

Allow advanced 12- and 24-word recovery to use one-based BIP39 word numbers. Resolve and confirm every word, retain the existing final-word calculation flow, and validate the complete recovery phrase before deriving keys. Clear sensitive entry state and displayed words when the flow exits.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new way to restore a Bitcoin wallet on a Blockstream Jade hardware device: instead of typing each recovery word, users can enter each word's one-based BIP39 number (for example, '1' for 'abandon'). The change also refactors the existing word-entry code and adds cleanup of sensitive on-screen state when the user exits. There is no direct evidence in the commit that this fixes an active security vulnerability, but it touches sensitive seed-recovery code and changes how user input is validated and cleared.

Recommended action

Review the new word-number recovery path for off-by-one errors, buffer overflows, and incorrect handling of the final checksum word. Verify that all sensitive buffers are cleared on every exit path and that the digit-entry UI cannot accept out-of-range values. Treat this as a normal security-sensitive feature commit rather than an emergency vulnerability fix unless additional incident data is provided.

Security signals we found

01

New user-input path for seed recovery (word numbers instead of words)

02

Refactoring of mnemonic input/validation helpers

03

Addition of SENSITIVE_PUSH/POP for local mnemonic buffers

04

Clearing of sensitive UI state on flow exit

05

Format-string hardening in snprintf calls

06

Removal of CONFIG_DEBUG_UNATTENDED_CI guards around mnemonic_new and mnemonic_recover

Risk score

Why this scored 27/100

Our methodology →
Potential impact 5/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 6/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.