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

fix(solana): check owner in predefined flow

Public commit record

What the developer wrote

Authored by Jakub Janků

80/100 · Strong
fix(solana): check owner in predefined flow

Only the Stake11111111111111111111111111111111111111 program makes
sense as the owner in the predefined staking flow.

Note that this should not be exploitable as the transaction should
fail on chain --- the Solana runtime should enforce that the Stake
program is the owner of the account that it is about to manipulate.
However, it is better to not hide it from the user that the transaction
contains unexpected params.

[no changelog]

(cherry picked from commit ea194d6eedea43c35c1c98ecf521a11e8554b960)
✓ 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 update tightens a Solana staking flow in Trezor firmware so that the device now verifies the staking account is owned by the legitimate Stake program before showing the user a friendly confirmation screen. Previously, a crafted transaction with a different owner could slip through the predefined staking prompt, though the Solana network itself would likely reject it. The change also fixes a missing display option in the claim flow.

Recommended action

No immediate user action required; ensure firmware is updated to a release containing this commit. Developers should review whether other predefined flows have similar owner/program checks.

Security signals we found

01

Missing input validation in a predefined transaction confirmation path

02

UI prompt could be shown for a transaction with an unexpected program owner

03

Defense-in-depth check added for Solana staking account owner

04

Secondary fix: missing argument passed to recipient confirmation UI

Risk score

Why this scored 35/100

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