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

fix: zcash seed fingerprint export issue

Public commit record

What the developer wrote

Authored by soralit

57/100 · Thin
fix: zcash seed fingerprint export issue
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a bug in how the Keystone 3 hardware wallet stores a Zcash 'seed fingerprint.' The function that saves the fingerprint forgot to record which account it belongs to. That could cause the wallet to mix up or misidentify which Zcash account the fingerprint is for, potentially leading to wrong address derivation, export of incorrect account data, or user confusion when verifying accounts. It is a data-association bug, not a classic remote exploit.

Recommended action

Review all callers and consumers of g_zcashUFVKcache to confirm accountIndex is now consistently set and read; add regression tests for multi-account Zcash seed fingerprint export; verify that uninitialized or stale accountIndex values cannot propagate to exported data or UI prompts.

Security signals we found

01

Missing state-field update in account-scoped setter

02

Potential stale/uninitialized account index in shared cache structure

03

Risk of cross-account data confusion for Zcash UFVK/fingerprint export

04

No bounds or input validation changes; fix is a single field assignment

Risk score

Why this scored 41/100

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