Conjure

Conjure allows anyone to create tokenized assets on Ethereum representing any asset you can imagine. The resulting Synths are fully collateralized by Ether and have their collateralization and value pegged via a powerfully flexible ability to combine multiple arbitrary price sources to produce a single reference price. Conjure is permissionless (akin to Uniswap or Balancer) and permits the creation of assets representing - for example - synthetic currencies, tokens from other blockchains, real world commodities, and exotic assets such as basket currencies and indices. For more information about Conjure, please visit https://conjure.finance/.

The bug bounty program is focused on the prevention of these negative impacts to its smart contracts:

Thefts and freezing of principal of any amount Theft of governance funds Minting unlimited Assets where users should be unable to

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.

Payouts are handled by the Conjure team directly and are denominated in USD. All payouts are done in ETH, USDC, or CNJ, at the discretion of the Conjure team.

For additional information, Conjure has provided the direct links to these smart contracts on their GitHub:

Conjure - https://github.com/ConjureFi/contracts-main/blob/main/contracts/Conjure.sol

EtherCollateral - https://github.com/ConjureFi/contracts-main/blob/main/contracts/EtherCollateral.sol

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

• Loss of user funds staked (principal) by freezing or theft
• Loss of governance funds
• Temporary freezing of funds for any amount of time
• Unable to call smart contract
• Unlimited minting

We are especially interested in receiving and rewarding vulnerabilities of the following types, as long as they result in impacts stated in the Impacts in Scope section of this bug bounty program:

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

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

Additionally, all oracle-based vulnerabilities and exploits are considered as out-of-scope, as users can choose their own Oracles and these could be malicious and cause problems with the contract, we assume all oracles to be secure and up for audit purposes.

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