How Solana smart contracts work
- Language
- Rust, written as native programs or with the Anchor framework
- Runtime
- The Sealevel parallel runtime executing SBF bytecode (Solana's eBPF variant), with programs kept stateless and all state held in accounts
Languages and tooling we review
- Rust
- Anchor
- Solana Program Library
Solana vulnerability classes we check
Bug classes that come from how Solana works, checked on every Solana audit alongside the usual logic and access control review.
- Missing signer and owner checks on accounts passed into an instruction
- Account substitution and type confusion between account types
- PDA seed collisions and unchecked bump seeds
- Cross-program invocations (CPI) to an attacker-supplied program
- Integer overflow that wraps silently in release builds unless overflow checks are on
- Closed accounts that can be revived within the same transaction
Solana audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Solana.
Why teams choose Cecuro for Solana
// Example finding severity: HIGH title: Missing access control on upgrade() impact: Arbitrary logic upgrade can brick the protocol recommendation: Restrict to time-locked admin + add emergency pause