Harvest Finance

Submit a Bug
02 December 2020
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

Harvest Finance automatically farms the highest yield available from the newest DeFi protocols, and optimizes the yields that are received using the latest farming techniques.

Harvest Finance is primarily interested in securing their smart contracts, which can be found at https://github.com/harvest-finance. Primary areas of concern are anything that causes loss of user funds or frozen funds from a smart contract hack.

Harvest Finance is secondarily interested in securing their website, which can be found at https://harvest.finance. Web vulnerability disclosures will be rewarded at a lower rate, relative to smart contract vulnerability disclosures.

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.

The final reward amount of critical smart contract bugs is capped at 10% of economic damage based on the vulnerability reported with a minimum payout of USD 50 000.

Theft of yield/interest is considered as Medium for this bug bounty program.

The following table is used for the classification of web and app bug reports. In the event of conflict with the Immunefi Vulnerability Severity Classification System, the classification on this table will be what is considered.

SeverityVulnerability
CriticalDeletion of site data, XSS/CSRF, ACE
HighDenial of Service, DoS ampliciation
MediumIncorrect modification of user data, leaking user data

All web and app bug reports must include a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected and require the submitter to resubmit with a PoC.

Vulnerabilities that require moderator-approved access in order to be exploited will only receive a maximum of 20% of the advertised reward. For Critical Smart Contract and Blockchain vulnerability reports, this 20% is applied after the cap of 10% of economic damage.

Payouts are handled by the Harvest Finance team directly and are denominated in USD. Payouts up to USD 100 000 are paid in USDC.

Smart Contract

Critical
Level
Up to USD $100,000
Payout
High
Level
USD $10,000
Payout
Medium
Level
USD $5,000
Payout
Low
Level
USD $2,500
Payout
Informational
Level
USD $0
Payout

Websites and Applications

Critical
Level
USD $5,000
Payout
PoC Required
High
Level
USD $2,500
Payout
PoC Required
Medium
Level
USD $1,000
Payout
PoC Required
Low
Level
USD $0
Payout
PoC Required
Informational
Level
USD $0
Payout

Assets in scope

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

  • Critical Smart Contract Impact
    Critical
    Impact
  • High Smart Contract Impact
    High
    Impact
  • Medium Smart Contract Impact
    Medium
    Impact
  • Low Smart Contract Impact
    Low
    Impact

Websites and Applications

  • Critical Websites and Applications Impact
    Critical
    Impact
  • High Websites and Applications Impact
    High
    Impact
  • Medium Websites and Applications Impact
    Medium
    Impact
  • Low Websites and Applications Impact
    Low
    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 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

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