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

apply note or pwd as b39 passphrase

Public commit record

What the developer wrote

Authored by scgbckbone

45/100 · Thin
apply note or pwd as b39 passphrase
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a new feature to the COLDCARD hardware wallet that lets users apply the text of a Secure Note or the value of a Secure Note password as their BIP-39 wallet passphrase. It also tightens how printable ASCII is checked in a few places. The change is user-facing and requires physical interaction, so it does not look like a remote exploit. However, because passphrases control which wallet is derived, any bug in how note text is sanitized or applied could cause a user to load an unexpected wallet or expose a note's contents as a passphrase.

Recommended action

Review the feature as a normal security-sensitive UX change rather than an active vulnerability. Verify that `is_b39pass_applicable()` cannot be bypassed via encoding, memoryview, or menu argument manipulation; confirm that `apply_as_b39_pass()` only runs after explicit user approval; and ensure the `rstrip()` behavior and printable-ASCII check are applied consistently before any passphrase is used. Consider whether offering stored note/password content as a passphrase increases phishing or shoulder-surfing risk, and whether the UI clearly warns the user before applying the value.

Security signals we found

01

New feature exposes stored Secure Notes / Passwords as BIP-39 passphrases

02

Input validation relies on length, printable-ASCII, and rstrip of trailing whitespace/tab/newline

03

Refactored text sanitization changes control-flow for message signing and PSBT message warnings

04

Tests assert that non-printable or over-length note content is not offered as passphrase

05

No vendor disclosure of a security bug or researcher attribution present in commit

Risk score

Why this scored 27/100

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