Harvest Finance

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.

Total Bounty Pool: USD 50 000

Verification

Verification of Harvest Finance’s bug bounty program on Immunefi is available at https://farm.chainwiki.dev/en/security

Rewards by Threat Level

Rewards are distributed according to the exploitability level of the vulnerability and its impact based on the Immunefi Vulnerability Severity Classification System. The payout for a bug report is first calculated by the consequence the vulnerability causes with its respective percentage reward multiplied by the total bounty pool. Afterwards, the exploitability level and its respective percentage is multiplied by that amount to determine the final payout for the bug report.

The maximum payout for a smart contract bug is $50,000, and the maximum payout for a web vulnerability is $5,000.

Consequence
Critical - Loss or freezing of smart contract funds	$50,000
High - Deletion of site data, XSS/CSRF, ACE	$10,000
Medium - Denial of service, DoS amplification	$5,000
Low - Incorrect modification of user data, Leaking user data	$2,500
None - No known exploit - best practices	$0

Exploitability
No access	100%
Ordinary access	100%
Moderator-approved access	20%
Privileged access (non-root)	0%
Physical access	0%

Payouts are handled by Harvest Finance directly and are denominated in USDC.

Prioritized Vulnerabilities

We are especially interested in receiving and rewarding vulnerabilities of the following types for Smart Contracts:

• Reentrancy vulnerabilities
• Unauthorized access
• Logic errors
• Integer over- or underflow
• Potential economic/financial attacks (e.g flash loans)

We are especially interested in receiving and rewarding vulnerabilities of the following types for web vulnerabilities:

• Remote Code Execution
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• Direct object reference
• Path Traversal
• DOM XSS
• SSL misconfigurations
• SPF configuration problems
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• 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
• Lack of liquidity

The following activities are prohibited by bug bounty program:

• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. Java, external plugin) as well as websites (e.g. SSO providers, advertising networks)
• Any testing with mainnet contracts and public testnet contracts
• Disassembly or reverse engineering of binaries for which source code is not published