03 December 2021
Live since
Yes
KYC required
$100,000
Maximum bounty

Program Overview

IDEX is the first Hybrid Liquidity DEX, combining a high-performance order book and matching engine with Automated Market Making (AMM). The platform blends the best of centralized and decentralized exchanges, with the performance and features of a traditional order book and the security and liquidity of an AMM. IDEX allows traders to get the best spreads, avoid failed transactions, and easily provide liquidity, all with the power of real limit and stop-loss orders.

For more information about IDEX, please visit https://idex.io/.

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

  • Thefts and freezing of custodied funds or unclaimed yield of any amount

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. 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. t.

All web/app bug reports must come with a PoC in order to be considered for a reward.

The following vulnerabilities are not eligible for a reward:

In addition to Immunefi’s Vulnerability Severity Classification System, IDEX classifies the following vulnerabilities for websites and applications as follows. In case of discrepancy, the one below will be followed.

Critical

  • Access to user wallet private key
  • Ability to steal or freeze user funds
  • Admin access
  • Ability to move user funds without wallet signature
  • Ability to edit exchange configuration, especially contract addresses in the Get Exchange response
  • Unauthorized access to critical infrastructure

High

  • SQL injection
  • Unauthorized access to user data, eg name, email
  • Access to private data without wallet signature
  • Ability to access data using an API key that does not have the permission that is required by the endpoint
  • Replay attacks

IDEX requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name, Email address, Residential address. The collection of this information will be done by the IDEX team.

Payouts are handled by the IDEX team directly and are denominated in USD. However, payouts are done in IDEX or stablecoins, with the choice of the ratio at the discretion of the team.

Smart Contract

Critical
Level
USD $100,000
Payout
High
Level
USD $10,000
Payout

Websites and Applications

Critical
Level
USD $10,000
Payout
PoC Required
High
Level
USD $1,000
Payout
PoC Required

Assets in scope

All smart contracts of IDEX can be found at https://github.com/idexio/idex-contracts-silverton, https://github.com/idexio/idex-farm, and https://github.com/idexio/idex-contracts-earnings-escrow. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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

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

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