Sovryn-logo

Sovryn

Sovryn is an on-chain decentralized trading and lending protocol deployed on RSK, a side chain of the Bitcoin blockchain-powered by merge-mining, and is governed by the community. The Sovryn protocol is controlled by its community and stakeholders. There is no single company, organization, or individual that represents or controls the Sovryn protocol.

RSK
Defi
Lending
Staking
Solidity
Maximum Bounty
$1,000,000
Live Since
03 March 2021
Last Updated
23 May 2023
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Added on
Websites and Applications - Web/App
18 April 2022
Target
Type
Added on
Websites and Applications - Web/App
18 April 2022
Target
Type
Added on
Smart Contract - Blockchain/DLT - Fast/BTC
18 April 2022
Target
Type
Added on
Smart Contract - Blockchain/DLT - FastBtc/ConfirmationNode
18 April 2022
Target
Type
Added on
Smart Contract - Blockchain/DLT - BiDirectional/FastBtc
18 April 2022
Target
Type
Added on
Smart Contract - Blockchain/DLT - Bridge/FastBtc
18 April 2022
Target
Type
Added on
Smart Contract
17 February 2022

Impacts in Scope

Critical
Critical Blockchain/DLT impact leading to direct economic damage
Critical
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Critical
Permanent freezing of funds
Critical
Protocol insolvency
Critical
Ability to execute system commands resulting in a financial loss
Critical
Extract Sensitive data/files from the server such as /etc/passwd resulting in a financial loss
Critical
Signing transactions for other users
Critical
Redirection of user deposits and withdrawals
Critical
Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
Critical
Wallet interaction modification resulting in financial loss
Critical
Direct theft of user funds
Critical
Tampering with transactions submitted to the user’s wallet

Out of scope

Program's Out of Scope information

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

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
  • Vulnerabilities primarily caused by browser/plugin defects
  • Any vulnerability exploit requiring CSP bypass resulting from a browser bug

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