Comdex

Comdex is a DeFi Infrastructure Layer for the Cosmos Ecosystem. It provides a variety of interoperable plug & play modules for projects to use to create their own DeFi platforms providing utility to the Cosmos community as well.

Our goal is to democratize finance by building an infrastructure layer optimized for aggregating cross-chain liquidity with a suite of cutting-edge DeFi products. The primary means of doing this is by providing modules built on the core primitives of finance, allowing builders to utilize them to launch DeFi applications.

As of now, The Comdex Ecosystem comprises of:

• Composite $CMST : crypto collateralized stablecoin, mintable through Harbor Protocol.
• Harbor Protocol: an interchain stablecoin protocol that enables the minting of the CMST stablecoin using various interchain assets as collateral.
• cSwap: a decentralized, IBC-enabled hybrid exchange combining both traditional AMM-based liquidity pools alongside an order book-based system
• Commodo: a decentralized, open-source, IBC-native, collateralized lending-borrowing platform on Cosmos

For more information about Comdex, please visit

• https://comdex.one/
• https://docs.comdex.one
• http://docs.harborprotocol.one
• http://docs.cswap.one
• https://docs.commodo.one

To set up local chain with all the apps do follow this instructions : https://github.com/comdex-official/comdex/tree/development/scripts/comdex_local_setup Above script will spin local network with all the initial setups of harbor, cswap and commodo protocol.

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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

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 Medium, High and Critical Blockchain/DLT/Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Medium, High and Critical Web/app bug reports also require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

All vulnerabilities marked in the https://github.com/comdex-official/audit-reports are not eligible for a reward.

This bug bounty program will also have a hard cap of 500,000 CMDX. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis. All remaining valid reports will have their rewards considered after the launch of the project.

Payouts are handled by the Comdex team directly and are denominated in USD. However, payouts are done in CMDX which will be vested for 6 months and will unlock linearly per block.

The apps are geo blocked for certain locations due to legalities.

All smart contracts of Comdex can be found at https://github.com/comdex-official/comdex. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Comdex that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical and High impacts.

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
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass

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