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

Refuse claims at too-short derivation paths

Public commit record

What the developer wrote

Authored by kdmukai

68/100 · Adequate
Refuse claims at too-short derivation paths

A claim of ours at the empty path (the master key), on an input or an
output, or at a one-level path on an input, is held as
PSBTUnsupportedDerivationPathError. No wallet writes an entry at these
paths, though embit would sign an input built on the master key. The
check runs after the claim loops, so a forged claim in the same input
or output is still the one reported.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This update hardens a Bitcoin signing device (SeedSigner) against trick transactions. Previously, a malicious or broken PSBT file could claim that the user's master key or an unusually short key path should be used to sign a payment. The device would have accepted that path and could have signed something the user did not expect. Now the software rejects such PSBTs with a clear warning and discards the transaction. The change is defensive: it does not fix a known theft, but it closes a risky edge case where the wrong key could be used.

Recommended action

Treat this as a security hardening patch and include it in the next release. Users building from source should update to a revision that includes this commit. No immediate incident response is required unless an older device is known to have signed an unexpected master-key or one-level-path transaction.

Security signals we found

01

New validation exception for unsupported derivation paths

02

Rejects master-key (empty path) claims on inputs and outputs

03

Rejects one-level derivation path claims on inputs

04

Held-finding precedence preserves reporting of forged ownership claims

05

UI blocks continuation and only allows discarding the transaction

06

Test cases demonstrate embit would sign master-key input before this patch

Risk score

Why this scored 66/100

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