Enzyme Finance

Submit a Bug
29 March 2021
Live since
No
KYC required
$400,000
Maximum bounty

Program Overview

Enzyme Finance, formerly known as Melon Protocol, is an Ethereum-based protocol for decentralized on-chain asset management. It is a protocol for people or entities to manage their wealth & the wealth of others within a customizable and safe environment. Enzyme empowers anyone to set up, manage and invest in customized on-chain investment vehicles.

More information about Enzyme Finance can be found in their docs and also here in the additional V4 docs.

This bug bounty program is focused around the Enzyme Finance smart contracts and app and is primarily concerned with the loss of user funds.

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 for critical smart contract vulnerabilities is capped at 10% of the funds at risk based on the vulnerability reported.

All web and app bug reports and smart contract bug reports must come with a PoC. If a bug report does not have a PoC it will be rejected with instructions to provide a PoC

All payouts are done by the Enzyme Finance team directly and are denominated in USD. Payouts are done in USDC up to USD $400,000.

Smart Contract

Critical
Level
USD $400,000
Payout
PoC Required
High
Level
USD $80,000
Payout
PoC Required
Medium
Level
USD $20,000
Payout
PoC Required
Low
Level
USD $2,000
Payout
PoC Required
Informational
Level
USD $0
Payout

Websites and Applications

Critical
Level
USD $10,000
Payout
PoC Required
High
Level
USD $5,000
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

Only web/app vulnerabilities that directly affect the listed web/app assets are accepted within the bug bounty program. All others are out-of-scope.

Audits are available at https://github.com/enzymefinance/protocol/tree/v4/audits.

Any prior bugs that have been found in the audit above are ineligible for 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

  • 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
  • Internal SSRF
  • Path Traversal
  • SPF Configuration Problems

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