Lido for Solana

Lido for Solana is a Lido-DAO governed liquid staking protocol for the Solana blockchain. Anyone who stakes their SOL tokens with Lido will be issued an on-chain representation of SOL staking position with Lido validators, called stSOL. Lido for Solana will work to integrate stSOL widely into the Solana DeFi ecosystem to enable stSOL users to make use of their staked assets in a variety of applications.

For more information about Lido, the parent project, please visit their main bug bounty program at https://immunefi.com/bounty/lido/.

For more information about Lido for Solana itself, please visit https://chorusone.github.io/solido/.

This bug bounty program is focused on their smart contracts, website, and application, and is focused on preventing the following impacts:

• Loss of user funds staked (principal) by freezing or theft
• Freeze of user funds
• Governance manipulation
• Denial of service on smart contracts
• Redirected funds by address modification
• Denial of service
• Leak of user data
• Injection of texts
• RCE

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC in order to be considered for a reward.

Smart Contracts Rewards Breakdowns

• Smart Contracts Critical:

  • Loss of user funds:
    • 1% of assets at risk, minimum 100 000 USD, maximum 2 000 000 USD
  • Loss of non-user funds (e.g. treasury):
    • 1% of assets at risk, minimum 50 000 USD , maximum 1 000 000 USD

• Smart Contracts High:

  • 1% of assets at risk when attack persists for 1 month
    • minimum 20 000 USD, maximum of 400 000 USD

• Smart Contracts Medium:

  • 1% of assets at risk when attack persists for 1 month
    • minimum 5 000 USD, maximum 100 000 USD

• Smart Contracts Low:

  • 2 000 USD

Web/App Rewards Breakdowns

• Web/App Critical:

  • 40 000 USD

• Web/App High:

  • 7 500 USD
  • If attack can modify the transaction users approve so it sends funds to the wrong address: then this reward increases to a total of 40 000 USD

• Web/App Medium:

  • 3 250 USD

• Web/App Low:

  • 500 USD

Payouts are handled by the Solido (Lido for Solana) department of the Lido team directly and are denominated in USD. Payouts can be done in ETH, DAI, RAI, or LDO, at the decision of the bug bounty hunter.

For the “Main Program”, only the on-chain program in the “program” subdirectory of the repository is in scope. The “cli” subdirectory is not. Please use the main branch.

For the “Multisig”, the addresses listed in the readme are the deployments of the upstream Serum Multisig program, these are not the addresses used by Lido for Solana. Please use the commit that is pinned as the “multisig” submodule in the solido repository.

Once launched on mainnet, the testnet addresses will be removed from the Assets in Scope table and replaced with mainnet contracts.

For researchers who want to start their research early, a development version is available at https://solana-dev.testnet.lido.fi/, but this devnet deployment is not in scope. Additionally, any web/app bugs not directly related to what is in the Assets in Scope table but relevant for lido.fi, should be submitted in their main bug bounty program, assuming it fulfills all other requirements.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

• Loss of user funds staked by freezing or theft
• Ability to gain more stSOL than the Solido exchange rate allows for a given SOL deposit
• Ability to gain more SOL than the Solido exchange rate allows for a given stSOL withdrawal
• Loss of governance funds (treasury or developer fees)
• Ability to manipulate manager-gated parameters without 4/7 multisig approval.
  • Changing the Solido fee percentages
  • Changing the validator list
  • Changing the maintainer list
  • Changing the multisig owner list
  • Upgrading the Solido or multisig program
• Ability to stake deposits without a signature from a maintainer
• Preventing Solido from making progress
  • Preventing users from depositing
  • Indefinitely preventing users from withdrawing
  • Preventing staking of new deposits
  • Preventing exchange rate updates
  • Preventing collecting validation rewards
  • Preventing validators from claiming their fee

Web/App

• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Accessing sensitive pages without authorization
• Injection of text
• Users spoofing other users
• Shell access on server

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solana details not considered
  • including integer over-/under-flow that does not fail the transaction
  • including balance dropping below the rent-exempt amount for essential accounts
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of compute units
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Reports about outdated dependencies
• Reports about vulnerabilities in dependencies, when those vulnerabilities do not impact Solido’s use of the dependency

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty