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

Measure the change window from the smallest input index

Public commit record

What the developer wrote

Authored by kdmukai

73/100 · Adequate
Measure the change window from the smallest input index

The address index window was measured from the largest non-hardened
address index among our inputs at the change's base path. An extra
input at a far index, which a coordinator can add, then widened the
window for every change output at that base path. Measured from the
smallest index, an added input can only narrow it. When every matching
input is at a hardened address index, the window is measured from 0.

An honest wallet spending an old utxo at a low index, with change far
past it, now gets the distant address warning. The user can still
continue.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a security check in SeedSigner, a small hardware-wallet-like device used to sign Bitcoin transactions. Previously, when deciding whether a change output's address was suspiciously far from the user's known addresses, the software measured from the largest input address index. A malicious transaction coordinator could add one extra input at a very high address index to widen the allowed window and sneak change into a distant, possibly attacker-controlled address without triggering a warning. The fix measures from the smallest input address index instead, so added high-index inputs can only narrow the window, not expand it. The commit also handles the edge case where all matching inputs use hardened (hidden) indices by measuring from zero.

Recommended action

Treat this as a security fix and include it in the next release. Users who build or install SeedSigner from source should update to a version containing this commit. Review any custom forks or downstream builds to ensure they apply the same change-output window logic. No immediate external incident response is indicated beyond normal patching.

Security signals we found

01

Fixes a window-widening attack against change-output verification

02

Change-output address index check now uses smallest input index instead of largest

03

Adds hardened-input edge-case handling (window measured from 0)

04

Includes updated and new unit tests for the corrected behavior

05

Commit message explicitly describes malicious-coordinator scenario

Risk score

Why this scored 60/100

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