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

fix(legacy): forbid removed Unchained path

Public commit record

What the developer wrote

Authored by Alejandro Pacheco

80/100 · Strong
fix(legacy): forbid removed Unchained path

- 82da663a86 removed the deprecated Unchained Capital pattern
`m/45'/coin_type'/account'/[0-1000000]/address_index`, but left the
five-element `m/45'` arm of `coin_path_check()` with no rejection for
a hardened `address_n[1]`. Such a path matches no pattern, yet it was
accepted as valid.
- With safety checks `Strict`, `GetAddress` showed the multisig address
of such a path (any account or address index, also a Bitcoin path on
Testnet) and `SignTx` signed a Bitcoin-path multisig input on Litecoin.
With `PromptTemporarily`, neither showed the unknown path warning.
- Reject it, as the other arms of coin_path_check() reject an unknown
pattern and as core does.

(cherry picked from commit ab9fd8af1ea8335a0270377891957dc56104b4d8)
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a bug in the Trezor Model One (legacy) firmware where an old, removed multisig key path pattern was still being accepted as valid. Because the path was treated as known, the device would show or sign with it without warning, even when the path belonged to one cryptocurrency (e.g., Bitcoin) but was used on another (e.g., Litecoin or Testnet). The fix makes the firmware reject this leftover pattern as an unknown path, matching the behavior of newer Trezor Core firmware.

Recommended action

Apply the patch to legacy firmware builds and run the added device tests (test_getaddress_show.py and test_signtx_invalid_path.py) to confirm that the removed Unchained path is rejected and that the PromptTemporarily warning flow is shown. Consider auditing other long-lived path-validation branches for similar half-removed patterns.

Security signals we found

01

Cross-coin key-path confusion: Bitcoin-derived multisig path accepted on Litecoin/Testnet

02

Missing unknown-path warning under PromptTemporarily safety checks

03

Inconsistent path validation between legacy and Core firmware

04

Deprecated/removed BIP-45-style Unchained Capital pattern still partially trusted

05

Address display and transaction signing possible for non-standard m/45' paths

Risk score

Why this scored 64/100

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