Creditum

Submit a Bug
12 April 2022
Live since
No
KYC required
$500,000
Maximum bounty

Program Overview

Launched by the team at Revenant Labs (formerly StakeSteak) on 8 January 2022, Creditum is a lending and borrowing protocol within the Fantom Ecosystem that allows users to borrow (or mint) cUSD, a stablecoin pegged at $1 USD, by posting different tokens as collateral. With access to cUSD, users are able to earn an annualized percentage yield (APY) on available farms to earn CREDIT, while maintaining exposure and gain access to other benefits as future projects are launched.

For more information about Creditum, please visit https://revenantlabs.io/.

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

  • Loss of user funds from any of the Liquidity pools
  • Exploit of credit, vecredit or cUSD token that lead to losses
  • Unapproved mints
  • User data leakage
  • Bugs that could cause the site to go down

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System and the Creditum bug bounty reward classification (see Impacts in Scope). 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 with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 100 000.

Payouts are handled by the Revenant Labs team directly and are denominated in USD. However, payouts are done in Credit.

Smart Contract

Critical
Level
Up to USD $500,000
Payout
PoC Required
High
Level
USD $100,000
Payout
PoC Required
Medium
Level
USD $10,000
Payout
Low
Level
USD $1,000
Payout

Websites and Applications

Critical
Level
USD $5,000
Payout
PoC Required

Assets in scope

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

  • Loss of user funds from any of the Liquidity pools
    Critical
    Impact
  • Exploit of credit, vecredit or cUSD token that lead to losses
    Critical
    Impact
  • Unapproved mints
    Critical
    Impact
  • Vesting contract errors leading to misappropriation of funds
    High
    Impact
  • Theft of unclaimed yields
    High
    Impact
  • Temporary freezing of funds for any amount of time
    High
    Impact
  • Attacks requiring access to leaked confidential keys/credentials
    High
    Impact
  • Smart contract gas drainage
    Medium
    Impact
  • Block stuffing without fund transfers blocked
    Medium
    Impact
  • Smart contract fails to deliver promised returns, but doesn’t lose value
    Low
    Impact

Websites and Applications

  • User data leakage - email addresses, discord usernames, wallet addresses etc…
    Critical
    Impact
  • Bugs that could cause the site to go down
    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 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
  • Vulnerabilities primarily caused by browser/plugin defects
  • Any vulnerability exploit requiring CSP bypass resulting from a browser bug

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