Compound

Submit a Bug
04 June 2021
Live since
Yes
KYC required
$50,000
Maximum bounty

Program Overview

Compound is a protocol on the Ethereum blockchain that establishes money markets, which are pools of assets with algorithmically derived interest rates, based on the supply and demand for the asset. Suppliers (and borrowers) of an asset interact directly with the protocol, earning (and paying) a floating interest rate, without having to negotiate terms such as maturity, interest rate, or collateral with a peer or counterparty.

Each money market is unique to an Ethereum asset (such as Ether, an ERC-20 stablecoin such as Dai, or an ERC-20 utility token such as Augur), and contains a transparent and publicly-inspectable ledger, with a record of all transactions and historical interest rates.

This bug bounty program is focused around the patches with the Comptroller implementation and the cToken implementation and the prevention of the loss of user funds and significant downtime of the smart contracts.

Rewards by Threat Level

Rewards for Smart Contract vulnerabilities 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.

Only bug reports that cause direct economic damage as stated in the Immunefi Vulnerability Severity Classification System for Critical level vulnerabilities are accepted within this bug bounty program. Vulnerabilities that cause a loss of yield may be considered if direct theft of USD 100 000 or greater can be executed.

For a vulnerability report to be considered for a reward, a proof of concept (PoC) must be included in the bug report, together with sufficient detail to enable Compound Labs engineers to quickly reproduce, understand, and fix the vulnerability.

Payouts are handled by Compound Labs directly and are denominated in USD. However, payouts are done in USDC.

Smart Contract

Critical
Level
USD $50,000
Payout

Assets in scope

Vulnerabilities caused by the effective changes made by the pull request listed in this table are considered as within scope of the bug bounty program, in addition to bugs in the changes themselves.

Vulnerabilities affecting any testnet components are not considered in-scope for this bug bounty program. Only mainnet components are considered as in-scope.

For reference, further details about these changes can be found here - https://www.comp.xyz/t/safety-and-gas-patches/1723

Terms and Conditions

  • To be eligible for bug bounty reward consideration, you must:

    • Be at least 18 years of age.
    • Be reporting in an individual capacity, or if employed by a company, reporting with the company’s written approval to submit a disclosure to Compound Labs.
    • Not be subject to US sanctions or reside in a US-embargoed country.
    • Not be a current or former Compound Labs employee, vendor, contractor, or employee of a Compound vendor or contractor.

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

  • Critical smart contract impact
    Critical
    Impact

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)
  • 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

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
  • Interacting with accounts that you do not own