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

fix(solana): fall back to generic UI for more ALT references

Public commit record

What the developer wrote

Authored by Jakub Janků

93/100 · Strong
fix(solana): fall back to generic UI for more ALT references

transfer_token_instruction.token_mint and
transfer_token_instruction.owner can be Address Lookup Table (ALT)
references. Previously, the predefined token transfer flow
would misleadingly display just the ALT address. The user thus
couldn't distinguish an actual address from an ALT reference.
Now, the handler falls back to the generic ALT-aware confirmation UI.

537b34f847f8e3f97e4444be9f8f50706ac34075 added a check for
transfer_token_instruction.destination_account, but omitted
the token_mint and owner fields which can be ALT references
as well.

Partially fixes: https://github.com/satoshilabs/trezor-firmware/issues/325

(cherry picked from commit b992a24a93d77066b3ac2fec1dae7129d09427d1)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This update fixes a display bug in Trezor's Solana token-transfer confirmation screen. When a token transfer uses Solana Address Lookup Tables (ALTs) to refer to the token mint or the owner account, the device previously showed the lookup-table address as if it were the real account address. That could trick a user into approving a transfer they did not fully understand. The fix makes these cases fall back to a more cautious, generic confirmation screen that clearly marks ALT references.

Recommended action

Treat as a security-hardening fix with user-impact. Users should update firmware when available. Developers reviewing Solana transaction flows should verify that any account field that can be an ALT reference is handled by the generic ALT-aware UI rather than the predefined flow.

Security signals we found

01

UI spoofing / misleading display of account addresses

02

Address Lookup Table (ALT) reference not resolved on-device

03

User confirmation bypass risk due to incorrect address rendering

04

Security changelog entry present

Risk score

Why this scored 61/100

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