BendDAO
Submit a BugProgram Overview
Bend DAO is the first decentralized peer-to-pool based NFT liquidity protocol. Borrowers can borrow ETH instantly through the lending pool using NFTs as collateral. Depositors provide ETH liquidity to the lending pool to earn interest.
For more information about BendDAO, please visit https://www.benddao.xyz/. This bug bounty program is focused on smart contracts, website and app, and is focused on preventing:
- Loss of user NFTs
- Loss of user ETH
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 Smart Contract bug reports require a PoC and 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.
All vulnerabilities marked in the Security Audit Reports are not eligible for a reward.
Payouts are handled by the BendDAO team directly and are denominated in USD. However, payouts are done in BEND.
Smart Contract
- Critical
- Level
- Up to USD $1,000,000
- Payout
- High
- Level
- USD $10,000
- Payout
- Medium
- Level
- USD $2,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Websites and Applications
- Critical
- Level
- USD $20,000
- Payout
- High
- Level
- USD $4,000
- Payout
- Medium
- Level
- USD $2,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - ProxyAdminType
- Smart Contract - BNFTRegistry ProxyType
- Smart Contract - boundWPUNKS ProxyType
- Smart Contract - AirdropFlashLoanReceiverType
- Smart Contract - BendProxyAdminPoolType
- Smart Contract - BendProxyAdminFundType
- Smart Contract - BendCollector ProxyType
- Smart Contract - LendPoolAddressesProviderRegistryType
- Smart Contract - LendPoolAddressesProviderType
- Smart Contract - NFTOracle ProxyType
- Smart Contract - ReserveOracle ProxyType
- Smart Contract - LendPool ProxyType
- Smart Contract - LendPoolConfigurator ProxyType
- Smart Contract - LendPoolLoan ProxyType
- Smart Contract - bendWETH ProxyType
- Smart Contract - bendDebtWETH ProxyType
- Smart Contract - WETHGateway ProxyType
- Smart Contract - PunkGateway ProxyType
- Smart Contract - ProxyAdminType
- Smart Contract - BendToken ProxyType
- Smart Contract - MerkleDistributor ProxyType
- Smart Contract - Vault ProxyType
- Smart Contract - BendProtocolIncentivesController ProxyType
- Smart Contract - VeBend ProxyType
- Smart Contract - FeeDistributor ProxyType
- Smart Contract - BendKeeperType
- Smart Contract - LockupBendFactory ProxyType
- Smart Contract - BendCompetition ProxyType
- Smart Contract - BNFTRegistry ImplementationType
- Smart Contract - BNFT ImplementationType
- Smart Contract - BendCollector ImplementationType
- Smart Contract - NFTOracle ImplementationType
- Smart Contract - ReserveOracle ImplementationType
- Smart Contract - LendPool ImplementationType
- Smart Contract - LendPoolConfigurator ImplementationType
- Smart Contract - LendPoolLoan ImplementationType
- Smart Contract - bendWETH ImplementationType
- Smart Contract - bendDebtWETH ImplementationType
- Smart Contract - WETHGateway ImplementationType
- Smart Contract - PunkGateway ImplementationType
- Smart Contract - BendToken ImplementationType
- Smart Contract - MerkleDistributor ImplementationType
- Smart Contract - Vault ImplementationType
- Smart Contract - BendProtocolIncentivesController ImplementationType
- Smart Contract - VeBend ImplementationType
- Smart Contract - FeeDistributor ImplementationType
- Smart Contract - LockupBendFactory ImplementationType
- Smart Contract - BendCompetition ImplementationType
- Smart Contract - BendExchangeType
- Smart Contract - AuthorizationManagerType
- Smart Contract - CurrencyManagerType
- Smart Contract - ExecutionManagerType
- Smart Contract - RoyaltyFeeRegistryType
- Smart Contract - RoyaltyFeeSetterType
- Smart Contract - RoyaltyFeeManagerType
- Smart Contract - TransferERC721Type
- Smart Contract - TransferERC1155Type
- Smart Contract - TransferManagerType
- Smart Contract - InterceptorManagerType
- Smart Contract - RedeemNFTType
- Smart Contract - StrategyStandardSaleForFixedPriceType
- Smart Contract - Downpayment ProxyType
- Smart Contract - OpenSeaAdapter ProxyType
- Smart Contract - SeaportAdapter ProxyType
- Smart Contract - PunkAdapter ProxyType
- Smart Contract - X2Y2Adapter ProxyType
- Smart Contract - LooksRareExchangeAdapter ProxyType
- Smart Contract - BendExchangeAdapter ProxyType
- Smart Contract - Downpayment ImplementationType
- Smart Contract - OpenSeaAdapter ImplementationType
- Smart Contract - SeaportAdapter ImplementationType
- Smart Contract - PunkAdapter ImplementationType
- Smart Contract - X2Y2Adapter ImplementationType
- Smart Contract - LooksRareExchangeAdapter ImplementationType
- Smart Contract - BendExchangeAdapter ImplementationType
- Smart Contract - BendApeStaking ProxyType
- Smart Contract - BendApeStaking ImplementationType
- Smart Contract - StakeManager ProxyType
- Smart Contract - StakeManager ImplementationType
- Smart Contract - StakeProxy ImplementationType
- Smart Contract - NftVault ProxyType
- Smart Contract - NftVault ImplementationType
- Smart Contract - StBAYC ProxyType
- Smart Contract - StBAYC ImplementationType
- Smart Contract - StMAYC ProxyType
- Smart Contract - StMAYC ImplementationType
- Smart Contract - StBAKC ProxyType
- Smart Contract - StBAKC ImplementationType
- Smart Contract - BendCoinPool ProxyType
- Smart Contract - BendCoinPool ImplementationType
- Smart Contract - BendNftPool ProxyType
- Smart Contract - BendNftPool ImplementationType
- Smart Contract - BendStakeManager ProxyType
- Smart Contract - BendStakeManager ImplementationType
- Smart Contract - BaycRewardsStrategyType
- Smart Contract - MaycRewardsStrategyType
- Smart Contract - BakcRewardsStrategyType
- Smart Contract - DefaultWithdrawStrategyType
- TargetWebsites and Applications - Main Web AppType
All smart contracts code of BendDAO can be found at https://github.com/BendDAO. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy and implementation smart contract as the target.
If an impact can be caused to any other asset managed by BendDAO that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical and High impacts.
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
- Any governance voting result manipulationCriticalImpact
- Direct theft of numerous user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of funds of numerous userCriticalImpact
- InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Direct theft of individual user funds, whether at-rest or in-motion, other than unclaimed yieldHighImpact
- Permanent freezing of funds of individual userHighImpact
- Smart contract unable to operate and call ( e.g. destruct of code, lack of funds)MediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
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
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- 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
- 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
- Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.HighImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notificationMediumImpact
- Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site dataMediumImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
- Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)LowImpact
- Any impact involving a publicly released CVE without a working PoCLowImpact
- Taking over broken or expired outgoing links such as social media handles, etc.LowImpact
- 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
- Centralization risks
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 reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- 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
- Denial of service vulnerabilities (e.g. rate limit)
- Third-party service vulnerabilities
- Any behavior of phishing and social engineering on users
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