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

fix(solana): verify accounts in sysvar slots

Public commit record

What the developer wrote

Authored by Jakub Janků

90/100 · Strong
fix(solana): verify accounts in sysvar slots

- The Stake program v5 made the sysvar accounts optional and picks the
account layout by checking whether the sysvar slot holds the sysvar,
so another account there shifts the following accounts into roles
different from the ones shown on the device.
- Solana is moving away from sysvar account references in program ABIs
in general, so reject anything but the named sysvar in these slots to
catch similar changes in other programs as well.
- Fix the claim fixtures that passed the ComputeBudget program as the
stake history sysvar.

Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
(cherry picked from commit 9b4b571e3c4c406a7cb5dda0e097647f91f218e4)
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This update fixes a security issue in how Trezor handles Solana transactions. Some Solana programs use special 'sysvar' accounts in fixed slots. A malicious transaction could put a different account into one of those slots, causing the device to interpret the remaining accounts incorrectly and approve a transaction that looks safe on screen but does something else on the blockchain. The fix makes the device reject any transaction where a sysvar slot does not contain the exact expected sysvar account.

Recommended action

Apply the patch and ensure generated instructions.py is rebuilt from the updated .mako template. Run the new TestSolanaSysvarAccounts tests and the corrected staking transaction fixtures. Consider auditing other program parsers that rely on positional account semantics for similar slot-validation gaps.

Security signals we found

01

UI-to-blockchain account role mismatch

02

Missing validation of expected sysvar account public keys

03

Version-0 address lookup table references bypass static verification

04

Changelog explicitly labels change as security-relevant

05

Fixtures previously contained an incorrect sysvar account

Risk score

Why this scored 76/100

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