Warp Finance

Submit a Bug
15 February 2021
Live since
No
KYC required
$50,000
Maximum bounty

Program Overview

Warp V2, the Blacksmith upgrade, will provide a platform for users to create isolated lending pairs for more niche assets that are not currently serviced by other lending protocols, with the added benefit of each having its own risk/reward ratio.

Warp V2 aims to pioneer the unlocking of capital efficiency by freeing the potential of illiquid yield generating assets, thus providing holders of these assets with previously unavailable opportunities to leverage these tokens.

The development roadmap for Warp V2 includes further innovation within the DeFi space, such as the ability of users to create their own lending pairs, the creation of pool based lending pairs, and the ability for users to use L2 assets as collateral on L1.

Warp Finance is interested in securing its smart contracts, primarily around preventing loss of user funds, with UI issues (wrong values), and with confirmation/metamask integration issues.

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.

Payouts are handled by Warp Finance directly and are estimated in USD. The payout can only be completed in WARP.

Smart Contract

Critical
Level
USD $50,000
Payout
High
Level
USD $10,000
Payout
Medium
Level
USD $5,000
Payout
Low
Level
USD $1,000
Payout
Informational
Level
USD $0
Payout

Websites and Applications

Critical
Level
USD $7,500
Payout
High
Level
USD $3,250
Payout
Medium
Level
USD $1,000
Payout
Low
Level
USD $0
Payout
Informational
Level
USD $0
Payout

Assets in scope

Files in the Test and FakeTokens folders are out of 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 Contract

  • Loss of user funds by freezing or theft
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds
    High
    Impact
  • Unable to call smart contract
    Medium
    Impact
  • Smart contract gas drainage
    Medium
    Impact
  • Smart contract fails to deliver promised returns
    Low
    Impact

Websites and Applications

  • Critical Web/App impact
    Critical
    Impact
  • High Web/App impact
    High
    Impact
  • Medium Web/App Impact
    Medium
    Impact

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

Other Notes

In your reports, please include:

  • Screenshots
  • Error messages (if any)
  • Descriptions