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
AMM
Bridge
DAO
DEX
Lending
Staking
Token
Solidity
Typescript
Python
Maximum Bounty
$1,000,000
Live Since
03 March 2021
Last Updated
02 October 2025
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Target
Type
Blockchain/DLT - Bridge
Added on
18 April 2022
Target
Type
Blockchain/DLT - Blockchain/DLT - FastBTC
Added on
18 April 2022
Target
Type
Blockchain/DLT - BiDirectional/FastBTC
Added on
18 April 2022
Target
Type
Blockchain/DLT - FastBTC/ConfirmationNode
Added on
18 April 2022
Target
Type
Websites and Applications - Web/App
Added on
18 April 2022
Target
Type
Websites and Applications - Web/App
Added on
18 April 2022

Impacts in Scope

Severity
Critical
Title

Critical Blockchain/DLT impact leading to direct economic damage

Severity
Critical
Title

Ability to execute system commands resulting in a financial loss

Severity
Critical
Title

Extract Sensitive data/files from the server such as /etc/passwd resulting in a financial loss

Severity
Critical
Title

Signing transactions for other users

Severity
Critical
Title

Redirection of user deposits and withdrawals

Severity
Critical
Title

Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)

Severity
Critical
Title

Wallet interaction modification resulting in financial loss

Severity
Critical
Title

Tampering with transactions submitted to the user’s wallet

Severity
Critical
Title

Submitting malicious transactions to an already-connected wallet

Severity
Critical
Title

Direct theft of user funds

Severity
High
Title

High Blockchain/DLT impact leading to direct economic damage

Severity
High
Title

Privilege escalation to access unauthorized functionalities

Out of scope

Program's Out of Scope information
Default Out of Scope and rules

Web & App specific

  • Theoretical impacts without any proof or demonstration
  • Impacts involving attacks requiring physical access to the victim device
  • Impacts involving attacks requiring access to the local network of the victim
  • Reflected plain text injection (e.g. url parameters, path, etc.)
    • This does not exclude reflected HTML injection with or without JavaScript
    • This does not exclude persistent plain text injection
  • Any impacts involving self-XSS
  • Captcha bypass using OCR without impact demonstration
  • CSRF with no state modifying security impact (e.g. logout CSRF)
  • Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
  • Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
  • Impacts causing only the enumeration or confirmation of the existence of users or tenants
  • Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
  • Lack of SSL/TLS best practices
  • Impacts that only require DDoS
  • UX and UI impacts that do not materially disrupt use of the platform
  • Impacts primarily caused by browser/plugin defects
  • Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
  • Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
  • SPF/DMARC misconfigured records)
  • Missing HTTP Headers without demonstrated impact
  • Automated scanner reports without demonstrated impact
  • UI/UX best practice recommendations
  • Non-future-proof NFT rendering

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers