The Aloe Protocol is a liquidity allocator for AMMs, targeting Uniswap V3 at launch. Aloe Blend uses a hybrid liquidity management system that's designed to earn more trading fees for liquidity providers (LPs) without requiring them to select specific ranges or manually move their funds around. This is done through silos, which are adapters to arbitrary yield strategies that enable otherwise idle funds to earn extra yield.
For more information about Aloe Protocol, please visit https://docs.aloe.capital.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Low and Medium Smart Contract bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 10 000.
High smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 5 000.
The following vulnerabilities are not eligible for a reward:
- Aloe Blend is incompatible with fee-on-transfer tokens
deposit, the contract may slightly underestimate how many shares the depositor deserves. This is the case if and only if, during the next rebalance, the conditional on line 519 or 529 of
AloeBlend.solis true. Furthermore, the value forfeited by the depositor is less than 10% of yield earned since the last rebalance.
withdrawthe contract may slightly underestimate how many tokens are owed to the withdrawer. This is the case if and only if, during the next rebalance, the conditional on line 519 or 529 of
AloeBlend.solis true. Furthermore, the value forfeited by the withdrawer is less than 10% of yield earned since the last rebalance.
- Aloe Blend’s gas price oracle has insufficient precision to capture gas prices less than 1e-4 token units per gas unit. For example, USDC has 6 decimals, so gas price < 0.0001 USD/gasunit would not be recorded properly.
- Aloe Blend’s gas price oracle is vulnerable to an attack described here, but it’s designed to be expensive to execute and has minimal economic benefit for the attacker.
- Equations for implied volatility, position width, and limit order size are approximations. See here.
Aloe Labs requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a W9 or W8-BEN. This includes information like name, address, and taxpayer identification number. The collection of this information will be done by the project team.
Payouts are handled by the Aloe Labs team directly and are denominated in USD. However, payouts are done in USDC and USDT, with the choice of the ratio at the discretion of the reporters.
- Up to USD $50,000
- Up to USD $10,000
- USD $2,500
- USD $1,000
Websites and Applications
- USD $7,500
- USD $5,000
- USD $2,500
- USD $1,000
Assets in scope
- Smart Contract - Volatility OracleType
- Smart Contract - Compound WETH SiloType
- Smart Contract - Compound USDC SiloType
- Smart Contract - Yearn WBTC SiloType
- Smart Contract - Aloe Blend USDC/WETHType
- Smart Contract - Aloe Blend FEI/TRIBEType
- Smart Contract - Aloe Blend WBTC/WETHType
- Websites and Applications - Aloe Labs’ Web AppType
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.
- Theft of user funds from `AloeBlend.sol` instancesCriticalImpact
- Freezing of user funds in `AloeBlend.sol` instances for any amount of timeCriticalImpact
- Theft of Yield is considered Critical if the theft is greater than what the endangered entity (may be a specific Blend pool, set of pools, or protocol as a whole) generates in an average week.CriticalImpact
- Manipulation of `AloeBlend.sol`.CriticalImpact
- Any attack which causes pool performance to dip below the `sqrt(price)` baselineHighImpact
- Theft of unclaimed user yields from `AloeBlend.sol` instancesHighImpact
- Unbounded gas consumptionMediumImpact
- `rebalance` incentivization exploits that freeze incentives for more than 1 monthMediumImpact
- Oversights in contract efficiency (optimizations > 50000 gas)LowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking Down the application/websiteCriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.CriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
- Any impact involving a publicly released CVE without a working PoCLowImpact
- Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.LowImpact
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
- Macro-economic trends such as just-in-time liquidity (this may reduce users’ yield, but it is not a bug in Aloe)
- Attacks on the protocols with which Aloe is integrated (Uniswap, Compound, Rari Fuse, Yearn, etc)
- Loss/freezing of tokens other than the Blend pool’s primary tokens (
token1) unless the silo is specifically designed to collect them. For example, the Compound CToken Silos are not designed to collect COMP rewards, so COMP losses are out of scope
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude persistent plain text injection
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
The following activities are prohibited by this 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