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

fix(solana): show account owner to user

Public commit record

What the developer wrote

Authored by Jakub Janků

80/100 · Strong
fix(solana): show account owner to user

When assigning an `owner` to an account, using the `CreateAccount`,
`CreateAccountWithSeed`, or `AllocateWithSeed` instructions, it is
critical to display the value to the user. Usually, the owner is a
well-known Solana program, such as the System program
(11111111111111111111111111111111) or the Stake program
(Stake11111111111111111111111111111111111111). However, an attacker
could set the value to a Solana program that is controlled by them
and later drain money from the account. This is especially problematic
since the two `CreateAccount` instructions immediately send funds to
the new account.

[no changelog]

(cherry picked from commit d3f24b0f6739cdae93074c5a4f60658e15c456e0)
✓ 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 fixes a security gap in how Trezor displays Solana transactions. When creating or allocating a Solana account, the device now shows the 'owner' program that will control the new account. Before this change, a malicious owner could be hidden from the user, allowing an attacker to later seize funds sent to the freshly created account. The fix is purely a user-interface change on the hardware wallet screen, not a change to Solana itself.

Recommended action

Users should install firmware containing this commit and carefully verify the 'Owner' field when signing Solana CreateAccount, CreateAccountWithSeed, or AllocateWithSeed transactions. Developers should review other Solana instructions for similarly hidden security-sensitive parameters.

Security signals we found

01

Missing security-critical UI field for account ownership

02

Social-engineering / transaction-tampering vector via malicious owner program

03

Funds-at-risk because CreateAccount instructions deposit lamports immediately

04

Patch adds explicit user confirmation for owner pubkey

Risk score

Why this scored 76/100

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