28 December 2021
Live since
No
KYC required
$250,000
Maximum bounty

Program Overview

Revault brings the power of easy search navigation to the DeFi ecosystem, enabling anyone to find and deposit funds in the best performing vaults on any blockchain at any given time.

The REVA token incentivizes users to use Revault as their go-to gateway to DeFi. Using Revault, users will receive all the rewards from their selected vault plus rewards of our REVA tokens, making depositing through Revault’s search & maximize engine the best choice for any asset. Revault simply relays funds — they don’t compete with other vault projects on strategies or APY.

For more information about Revault, please visit https://www.revault.network/.

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

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

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 web/app bug reports must come with a PoC in order to be considered for a reward. Additionally suggestions for a fix must be provided for Medium web/app bug reports and higher.

For both smart contract bugs, a PoC must be provided for High and Critical vulnerabilities, and a suggestion for a fix must be provided for Medium smart contract bug reports and higher.

Please note that all resolved issues, and any open or partially resolved issues from either of our audits (Certik, Paladin) are out of the scope of the bug bounty.

Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum of USD 50 000 for Critical bug reports.

Payouts are handled by the Revault team directly and are denominated in USD. However, payouts are done in BUSD or REVA, at the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
Up to USD $250,000
Payout
high
Level
USD $25,000
Payout
medium
Level
USD $10,000
Payout
low
Level
USD $5,000
Payout

Web and Apps

Critical
Level
USD $10,000
Payout
high
Level
USD $5,000
Payout
medium
Level
USD $5,000
Payout

Assets in Scope

Further information about Revault can be found at https://github.com/Revault-network. However, only those 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 any amount of time
  • Unable to call smart contract
  • Smart contract gas drainage
  • Smart contract fails to deliver promised returns
  • Vote manipulation
  • Incorrect polling actions

Web/App

  • Site goes down
  • Accessing sensitive pages without authorization
  • Injection of text
  • Users spoofing other users
Smart Contract - REVA Token
Type
Smart Contract - vREVA Token
Type
Smart Contract - vREVA Token Deployment
Type
Smart Contract - Reva Chef (Proxy)
Type
Smart Contract - Reva Chef (Implementation)
Type
Smart Contract - Revault (Proxy)
Type
Smart Contract - Revault (Implementation)
Type
Smart Contract - REVA Fee Receiver (Proxy)
Type
Smart Contract - REVA Fee Receiver (Implementation)
Type
Smart Contract - REVA LP Fee Receiver (Proxy)
Type
Smart Contract - REVA LP Fee Receiver (Implementation)
Type
Smart Contract - REVA Staking Pool (Proxy)
Type
Smart Contract - REVA Staking Pool (Implementation)
Type
Smart Contract - REVA LP Staking Pool (Proxy)
Type
Smart Contract - REVA LP Staking Pool (Implementation)
Type
Smart Contract - Zap (Proxy)
Type
Smart Contract - Zap (Implementation)
Type
Smart Contract - ZapAndDeposit (Proxy)
Type
Smart Contract - ZapAndDeposit (Implementation)
Type
Smart Contract - REVA autocompund Stacking Pool (Proxy)
Type
Smart Contract - REVA autocompund Stacking Pool (Implementation)
Type
Web/App
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

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)

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
  • Centralization risks

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