Stone DeFi

Stone Protocol is the only yield management protocol focused on creating ‘Rock Solid Yield’ for all users in the DeFi ecosystem. The focus is developing innovative asset pools that maximizes return while keeping liquidity provider capital as safe and secure as possible. In doing so, we aim to create a robust passive income platform to meet the needs of the DeFi industry.

Stone is positioned as an anchor yield aggregation platform, and will eventually evolve to become a cross-chain asset aggregation and yield marketplace with the inclusion of multi-chain Proof of Stake (“POS”) assets such as Eth2.0 and Polkadot. With the inclusion of yield-bearing assets introduced by Stone, we will further create yield-based derivatives such as ‘Risk Optimized’ Yield indices and other derivatives.

For more information about Stone DeFi, please visit https://www.stonedefi.io/.

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

• Functional bugs
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Theft of governance funds
• Governance role take over
• Governance activity disruption
• Website goes down
• Leak of user data
• Deletion of user data
• Access to sensitive pages without authorization

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 Critical bug reports are required to have a PoC and a suggestion for a fix in order to receive a reward. All web/app bug reports are required to have a PoC.

Vulnerabilities involving any bug already disclosed in this audit are not eligible for a reward.

The payouts for Critical and High smart contract bug reports are in a fixed STN amount. The USD amounts are only provided as an estimate.

It is a known issue that the oracle price float reflects that profit was lost, but in reality it doesn’t cause any profit loss, as it only affects the user interface. Bug reports mentioning this are considered as out-of-scope.

Payouts are handled by the Stone DeFi team directly and are denominated in USD. However, payouts are done in STN for Critical and High smart contract vulnerabilities. Payouts for all other bug reports are done in STN or USDT, at the discretion of the team.

The GitHub for Stone DeFi can be found at https://github.com/stonedefi. However, only the things listed in the Assets in Scope table are considered as in-scope of the bug bounty program.

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 (principal) by freezing or theft
• Loss of governance funds
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds for at least 2 hours
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns
• Vote manipulation
• Incorrect polling actions

Web/App

• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Site goes down
• 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
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• 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 gas
  • 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)
• Feature Requests
• Best Practices

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

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

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