[REDACTED] Cartel

Submit a Bug
07 January 2022
Live since
No
KYC required
$1,000,000
Maximum bounty

Program Overview

[REDACTED] Cartel is a complimentary subDAO for OlympusDAO which aims to extend OlympusDAO’s influence to the greater DeFi ecosystem in an efficient and sustainable manner without making OlympusDAO stray away from its initial values (being reserve currency for DeFi space). [REDACTED] Cartel aims to achieve this by introducing the $BTRFLY token.

When interacting with [REDACTED] Cartel, a person holding a curve ecosystem token will bond their tokens through ‘metamorphosis’ and receive an equivalent amount of discounted $BTRFLY. By locking up curve ecosystem tokens to [REDACTED] Cartel treasury, they are essentially reducing the supply of these tokens from the secondary market. The tokens will be further used to aggregate yield strategies to grow the treasury and increase both $BTRFLY and curve ecosystem token’s intrinsic value.

[REDACTED] Cartel will have similar rebase tokenomics like OlympusDAO. Users can stake $BTRFLY and in exchange they will receive $xBTRFLY. Every epoch, rebase rewards will be allocated to the stakers. While [REDACTED] Cartel is focused on the Curve ecosystem, the DAO is looking to add more strategic risk assets, such as: FXS, TOKE and more.

For more information about [REDACTED] Cartel DAO, please visit https://www.redactedcartel.xyz/.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Theft of governance funds
  • Governance activity disruption

Rewards by Threat Level

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/app bug reports must come with a PoC in order to be considered for a reward. All Critical smart contract bug reports must come with a PoC in order to be considered for a reward

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 of USD 100 000 for Critical bug reports.

Payouts are handled by the [REDACTED] Cartel team directly and are denominated in USD. However, payouts are done in DAI, BTRFLY or a combination of both, at the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
Up to USD $1,000,000
Payout
high
Level
USD $100,000
Payout

Web and Apps

Critical
Level
USD $200,000
Payout
high
Level
USD $100,000
Payout

Assets in Scope

All smart contracts of [REDACTED] Cartel can be found at https://github.com/redacted-cartel. However, only those in the Assets in Scope table are considered as in-scope 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/Blockchain

  • Loss of user funds staked (principal) by freezing or theft
  • Loss of governance funds
  • Theft of unclaimed yield
  • Freezing of unclaimed yield
  • Temporary freezing of funds for at least 24 hours

Web/App

  • Redirected funds by address modification
  • Site goes down
  • Injection of text
  • Users spoofing other users
  • Shell access on server

Prioritized Vulnerabilities

We are especially interested in receiving and rewarding vulnerabilities of the following types:

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

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