BurgerSwap

Submit a Bug
09 December 2021
Live since
No
KYC required
$500,000
Maximum bounty

Program Overview

BurgerSwap is the first cross-chain aggregator that combines liquidity from the leading DEXs and CEXs, allowing users to access any digital asset or transfer funds between any chain on one platform at the best price.

This bug bounty program is focused on their smart contracts and is focused on preventing:

  • Loss of user funds staked (principal) by freezing or theft
  • Loss of governance funds
  • Theft of unclaimed yield

Rewards by Threat Level

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 Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.

The following vulnerabilities are not eligible for a reward:

  • Issues stated in the PeckShield security review are not eligible for a reward.
  • In Switch, Centralization / Privilege findings refer to either feature logic or implementation of components that act against the nature of decentralization, such as explicit ownership or specialized access roles in combination with a mechanism to relocate funds.

Payouts are handled by the BurgerSwap team directly and are denominated in USD. However, payouts are done in Burger and USDT, with the choice of the ratio at the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
Up to USD $500,000
Payout
high
Level
USD $10,000
Payout
medium
Level
USD $5,000
Payout

Assets in Scope

All smart contracts of BurgerSwap can be found at

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. For Switch contracts (multiple instances on different chains), there will not be duplicated counting of bugs. One bug that exists in all contracts will be counted as a single bug.

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/Blockchain

  • Loss of user funds staked (principal) by freezing or theft
  • Loss of governance funds
  • Theft of unclaimed yield
Smart Contract - Trade
Type
Smart Contract - Trade-liquidity
Type
Smart Contract - Aggregator
Type
Smart Contract - Switch-ETH-Across Proxy
Type
Smart Contract - Switch-ETH-Across
Type
Smart Contract - Switch-ETH-TicketFactory Proxy
Type
Smart Contract - Switch-ETH-TicketFactory
Type
Smart Contract - Switch-ETH-Farm Proxy
Type
Smart Contract - Switch-ETH-Farm
Type
Smart Contract - Switch-ETH-Pool Proxy
Type
Smart Contract - Switch-ETH-Pool
Type
Smart Contract - Switch-BSC-Across Proxy
Type
Smart Contract - Switch-BSC-Across
Type
Smart Contract - Switch-BSC-TicketFactory Proxy
Type
Smart Contract - Switch-BSC-TicketFactory
Type
Smart Contract - Switch-BSC-Pool Proxy
Type
Smart Contract - Switch-BSC-Pool
Type
Smart Contract - Switch-Heco-Across Proxy
Type
Smart Contract - Switch-Heco-Across
Type
Smart Contract - Switch-Heco-TicketFactory Proxy
Type
Smart Contract - Switch-Heco-TicketFactory
Type
Smart Contract - Switch-Heco-Farm Proxy
Type
Smart Contract - Switch-Heco-Farm
Type
Smart Contract - Switch-Heco-Pool Proxy
Type
Smart Contract - Switch-Heco-Pool
Type
Smart Contract - Switch-Matic-Across Proxy
Type
Smart Contract - Switch-Matic-Across
Type
Smart Contract - Switch-Matic-TicketFactory Proxy
Type
Smart Contract - Switch-Matic-TicketFactory
Type
Smart Contract - Switch-Matic-Farm Proxy
Type
Smart Contract - Switch-Matic-Farm
Type
Smart Contract - Switch-Matic-Pool Proxy
Type
Smart Contract - Switch-Matic-Pool
Type

Prioritized Vulnerabilities

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

Out of Scope & Rules

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

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