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

fix(core/delizia): correctly initialize `ConfirmAction` variants

Public commit record

What the developer wrote

Authored by Roman Zeyde

62/100 · Adequate
fix(core/delizia): correctly initialize `ConfirmAction` variants

[no changelog]
✓ Specific, 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 how the Trezor hardware wallet builds on-screen confirmation flows for the newer 'Delizia' interface. Previously, the code could register a confirmation page under the wrong internal state variant (for example, adding a confirmation screen to a flow that was not supposed to have one, or using the variant meant for flows with a menu when no menu existed). The patch makes the state variant explicit and passes it into the helper functions, ensuring each page is attached to the correct flow type. A mismatch could cause the device to show the wrong screen, ignore a button press, or behave unexpectedly when a user confirms or cancels an action.

Recommended action

Treat as a low-to-moderate reliability fix. Review whether the previous variant mismatch could lead to a skipped confirmation prompt or a stuck/crashed UI, and assess if any user action could be confirmed without the intended hold/tap interaction. If such a bypass is possible, request a security advisory and CVE; otherwise, include the fix in the next firmware release with a changelog note about UI flow robustness.

Security signals we found

01

UI state-machine inconsistency in security-critical confirmation flow

02

Possible wrong screen/page registration for hold-to-confirm / tap-to-confirm prompts

03

Possible mismatch between menu presence and confirmation state variant

04

Patch is marked [no changelog] and contains no explicit security disclosure

Risk score

Why this scored 46/100

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