Composable Finance

Composable Finance is creating infrastructure to unlock the multi-layer, and multi-chain future of Ethereum, and other layer 1 blockchains. At present, the lack of compatibility between blockchains and layers results in disparity and inefficiency. Developers are very restricted in what they can build with siloed infrastructures, and users are forced to navigate complicated and lengthy processes if they want to utilize multiple chains or layers.

With their products, Composable Finance intends to reduce these barriers that DeFi creators and users face.

For more information about Composable Finance, please read their introductory Medium blog post.

The bug bounty program covers its smart contracts and apps and is focused on receiving bug reports of the following impacts:

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Theft of governance funds
• Governance activity disruption
• Website goes down
• Leak of user data
• Deletion of user data
• Access to sensitive pages without authorization

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

All bug reports that are Medium or higher must come with a recommendation on how to fix the bug in order to qualify for a reward.

This bug bounty program has a total budget of USD 150 000. If there are simultaneous valid bug reports submitted, the rewards will be distributed on a first-come-first-serve basis, or at the discretion of the team. Additionally, the team may use up to 0.05% of the Composable Token supply to be designated as potential rewards for any other identified vulnerabilities after the USD 150 000 is exhausted.

Payouts are handled by the Composable Finance team directly and are denominated in USD. Payouts are done in ETH or USDC.

Only web/app vulnerabilities that directly affect the web/app assets listed in this table are accepted within the bug bounty program. All others are out-of-scope.

For added reference, please take a look at their GitHub - https://github.com/ComposableFi. However, only the contracts listed as in-scope here are considered as part of the bug bounty program.

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 Contracts

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns
• Anything else that would fall in the categories listed as Critical, High, and Medium

Website and Apps

• Frontend manipulation
• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Site goes down
• Accessing sensitive pages without authorization
• Injection of text
• Users spoofing other users
• Shell access on server

We are especially interested in receiving and rewarding attacks of the following types, as long as they result in the impacts in scope:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

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

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by 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