However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program

If a Critical or High severity impact can be caused to any other asset managed by Summer.fi 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 consideration by the project.

Summer.fi aims to be the most trusted entry point to deploy your capital into Decentralized Finance. You can now use it to borrow (generate) Dai and to Multiply the exposure to your favorite collateral assets, doing leverage-like trading. 

Unbounded gas consumption

Temporary freezing of funds for at least five blocks

Taking down the application/website temporarily with the possibility of restoring it

Ability to execute system commands

Extract Sensitive data/files from the server such as /etc/passwd

Stealing User Cookies

Subdomain takeover resulting in the financial loss (applicable for subdomains with addresses published)

Corrupting the database

Unauthorized access resulting in griefing to the user

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the smart contracts)

Smart contract fails to deliver promised returns, but doesn’t lose value

Misusing underlying protocols and services

Spoofing content on the target application (Persistent)

Subdomain Takeover without a financial loss (applicable for subdomains with no addresses published)

Changing details of other users without direct financial impact (CSRF)

Third-Party API keys leakage that demonstrates loss of funds or modification on the website

Redirecting users to malicious websites (open redirect)

Privilege escalation to access unauthorized functionalities

Users Confidential information disclosure such as Email

Bypassing Authentication

Any sort of loss of user funds, direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Causing any sort of economical damage to the smart contracts or the users (e.g. unbounded or unacceptable slippage)

Unauthorized access resulting in the loss of funds

Attacks leading to repeatable and unequivocal loss or permanent locking of user funds e.g: Direct theft of user, signing transactions for other users, redirection of user deposits and withdrawals, wallet interaction modification resulting in financial loss

Taking down the application/website permanently without the possibility of restoring it (Persistent)

Attacks leading to repeatable, unequivocal loss or permanent locking of user funds: tampering with transactions submitted to users wallet, submitting malicious transactions to connected wallet, submitting incorrect transactions due to the application error

Summer.fi Smart Contracts

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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 and Critical/High/Medium severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, Critical/High severity bug reports must also come with a suggestion for a fix in order to be considered for a reward. 

Previously highlighted vulnerabilities in the following security reviews are considered as out-of-scope:
  - [https://chainsecurity.com/wp-content/uploads/2021/09/ChainSecurity_Oazo_Apps_Limited_Multiply_Smart-Contract-audit_-September-7th-2021.pdf](https://chainsecurity.com/wp-content/uploads/2021/09/ChainSecurity_Oazo_Apps_Limited_Multiply_Smart-Contract-audit_-September-7th-2021.pdf) 
  - [https://chainsecurity.com/wp-content/uploads/2021/10/ChainSecurity_Oazo_Apps_Limited_Multiply_FMM_extension_audit.pdf ](https://chainsecurity.com/wp-content/uploads/2021/10/ChainSecurity_Oazo_Apps_Limited_Multiply_FMM_extension_audit.pdf)
  - [https://chainsecurity.com/security-audit/oasis-app-modular-proxy-actions/](https://chainsecurity.com/security-audit/oasis-app-modular-proxy-actions/)

The domain [https://legacy.oasis.app/](https://legacy.oasis.app/) and [https://legacy.summer.fi/](https://legacy.summer.fi/) is considered as out of scope of this program. 

Summer.fi utilises third-party smart contracts and services (e.g. Maker Protocol, 1Inch, GUNI, etc.). The below rules apply to vulnerabilities in the underlying protocols and services:
  - Only the smart contracts, websites and applications developed by the Summer.fi team are in the scope of this bug bounty program and are eligible for a reward. 
  - Vulnerabilities in the underlying protocols and services might be eligible for their dedicated bug bounty programs.
  - The Summer.fi team will facilitate the communication related to the reported vulnerabilities in the underlying protocols and services.

At the moment the Summer.fi team is focusing on the new smart contract architecture, which utilizes actions within Operations to tie DeFi together.

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of __USD 10 000__ for Critical smart contract bug reports, and a maximum reward of __USD 100 000__ for Critical smart contract bug reports.

Payouts are handled by the __Summer.fi__ team directly and are denominated in USD. However, payouts are done in __DAI__.

Title	Description	Link
Summer.fi Smart Contracts	New modular smart contract architecture
Summer.fi Smart Contracts	Multiply
Summer.fi Smart Contracts	Automation Stop-Loss

Summer.fi

Codebase