Blue by Enzyme Finance 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.
Triaged by Immunefi
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
These accepted impacts are then based on the severity classification system of this bug bounty program. When submitting a bug report, please select the severity level you feel best corresponds to the severity classification system as long as the impact itself is one of the listed items.
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds
Smart contract unable to operate due to lack of token funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Out of scope
Out of Scope reports:
- GatedRedemptionQueueSharesWrapperLib used with sharesActionTimelock
- first depositor share inflation attack
- GMX V2 case where adjustedClaimable < claimedAmount
- missing wrapped-native fallback in redeemFromQueue dispersal leads to griefing of native-asset batch redemptions
- malicious vault owner
- external position can be removed with negative value (debt)
- taking ETH/tokens accidentally sent directly to the contract outside intended protocol flows, without demonstrating how such funds can be introduced through valid protocol interactions. Common example: reports claiming an attacker can drain tokens from an adapter due to a missing onlyIntegrationManager check are invalid if the funds can only exist there via accidental direct transfers, or other non-protocol flows.
- front-running contract initialization during deployment. Contracts are deployed via factory contracts, which invoke the init function in the same transaction as the deployment, preventing attackers from front-running the initialization step.
Known issues:
- Incorrect share price for depositors and redeemers if "auto-buyback of protocol fee shares" is used Issue: During deposit and redeem, if a fund has autoProtocolFeeSharesBuyback turned on, an incorrect share price is constructed as: pre-buyback GAV / post-buyback total supply.
Effect: Results in too-high share price used to deposit or redeem shares
Mitigation: while mis-pricing should generally be small, unless you are confident in assessing impact, avoid using autoProtocolFeeSharesBuyback .
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers