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

fix(core): ignore unexpected messages in backup flow

Public commit record

What the developer wrote

Authored by Roman Zeyde

77/100 · Adequate
fix(core): ignore unexpected messages in backup flow

I/O errors and timeouts are not handled.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
The short version

What changed, and why it matters

This update changes how the Trezor hardware wallet handles unexpected messages while creating a seed backup. Previously, stray or hostile messages (such as a 'Cancel' command) could interrupt the backup process and leave the wallet in an unclear or partially-backed-up state. The fix wraps the backup flow in a new 'continue on errors' mode that ignores unexpected traffic and tells the host the device is busy, so the backup runs to completion. The change is defensive and improves reliability, but it also means a user can no longer cancel a backup from the host side once it has started.

Recommended action

Review whether the broader 'ignore all unexpected messages' behavior is appropriate only for backup, or whether it should be scoped more narrowly. Ensure that legitimate user cancellation via device buttons still works, and that the InProgress response cannot be abused to keep the device unresponsive indefinitely. Consider adding explicit timeout handling as noted in the commit message ('I/O errors and timeouts are not handled').

Security signals we found

01

Denial-of-service / workflow interruption: previously an unexpected message could abort the backup flow

02

Defensive hardening: backup flow now ignores unexpected host messages and continues

03

Behavior change: host-initiated cancellation of an in-progress backup is no longer honored on Core models

04

New FailureType.InProgress response sent to host when an unexpected message arrives during backup

Risk score

Why this scored 48/100

Our methodology →
Potential impact 12/30
Exploitability 10/25
Stealth signal 6/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.