IDEX

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/.

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

The following vulnerabilities are not eligible for a reward:

• Vulnerabilities marked as “Acknowledged” in the Quantstamp security review
• Issues involving token contracts that manipulate deposited funds or prevent deposited fund movement outside of the service’s control.
• Issues and behavior already described in documentation and linked sources:
  • https://api-docs-v3.idex.io/
  • https://github.com/idexio/idex-contracts-silverton/blob/main/README.md
  • https://github.com/idexio/idex-farm/blob/main/README.md
  • https://github.com/idexio/investigations

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.

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.

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