Zest Protocol Smart Contracts: Program info

Documentation

• Program Documentation — https://docs.zestprotocol.com/start
• Program Codebase — https://github.com/Zest-Protocol/zest-contracts/tree/main/onchain/contracts/borrow

IN SCOPE: SMART CONTRACT VULNERABILITIES

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.

• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield (Critical Impact)
• Permanent freezing of funds (Critical Impact)
• Protocol insolvency (Critical Impact)
• Theft of unclaimed yield (High Impact)
• Theft of unclaimed royalties (High Impact)
• Permanent freezing of unclaimed yield (High Impact)
• Permanent freezing of unclaimed royalties (High Impact)
• Temporary freezing of funds (High Impact)

OUT OF SCOPE: SMART CONTRACT VULNERABILITIES

• Lines of code that are not in the transfer-to-user function in pool-0-reserve: https://github.com/Zest-Protocol/zest-contracts/blob/main/onchain/contracts/borrow/production/vaults/pool-0-reserve.clar
• Scenarios where the function get-base-supply-rate returns a value that is not u0 here: https://github.com/Zest-Protocol/zest-contracts/blob/main/onchain/contracts/borrow/production/vaults/pool-0-reserve-v2-0.clar

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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• 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

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

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• Zest Protocol’s codebase can be found at https://github.com/Zest-Protocol/zest-contracts/tree/main/onchain/contracts/borrow . Documentation and further resources can be found on https://docs.zestprotocol.com/start/.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps