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

usb: add descriptor export for unlocked devices

Public commit record

What the developer wrote

Authored by Austin-Fulbright

60/100 · Adequate
usb: add descriptor export for unlocked devices

Does not currently support Liquid or Green multisig.

Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit adds a new feature to Blockstream Jade hardware wallets that lets the user export an extended public key (xpub) as a file to a connected USB storage device. The feature only works when the device is unlocked and explicitly disallows multisig exports. It is a normal product feature, not a fix for a known security bug. There is no evidence in the commit or supplied references that this is a security patch or that it addresses any disclosed vulnerability.

Recommended action

Treat as a feature addition rather than a security patch. Reviewers should verify that the user must explicitly approve the export on-device, that the exported file is written only after unlock, and that the 512-byte descriptor buffer cannot overflow for any script_variant/path/account_index combination. Consider whether the exported xpub file should be encrypted or whether the UI should warn the user that the file contains sensitive wallet information.

Security signals we found

01

New feature exposes xpub to external USB storage, increasing data-exfiltration surface if an attacker can trick the user into exporting or access the USB device afterward.

02

Multisig is explicitly disabled for descriptor export, reducing scope.

03

Liquid and Green multisig are noted as unsupported in the commit message.

04

No input validation or bounds checks beyond JADE_ASSERT are visible for the constructed descriptor buffer.

05

No evidence of a vulnerability fix, CVE, or security advisory in the commit or supplied references.

Risk score

Why this scored 24/100

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