Exponent

Exponent is a decentralized Capital-as-a-Service (CaaS) protocol. The protocol equips decentralized application (dApp) developers with the tools and services to offload and streamline capital management through smart contracts. Three main components make up the protocol: Vault - a one-stop capital management infrastructure, Middleware - application-specific logic and strategies, and Strategy generation - return generation and volatility managed DeFi products

This Bug Bounty program focuses on the Vault module, which is currently in beta. Multiple components make up the vault: Ex-ETH - ERC20 tokens representing shares of the vault, XPN Main - the contract with core business logics, and Issuance - the contract that streamlines and batch deposits capital into the Exponent vault. At the moment, the XPNSignal contract is not being utilized . The Exponent set of contracts is developed on top of Enzyme Finance’s infrastructure.

For more information about Exponent, please visit https://exponent.cx/.

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

• Any governance voting result manipulation
• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Permanent freezing of funds
• Miner-extractable value (MEV)
• Insolvency

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.

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 to be eligible for a reward.

The following vulnerabilities are not eligible for a reward:

• Known issues found and shared at https://docs.exponent.cx/
• Vulnerabilities marked in the Quantstamp security review are not eligible for a reward.

Payouts are handled by the Exponent team directly and are denominated in USD. However, payouts are done in USDC.

Smart Contract

Websites and Applications

All smart contracts of Exponent can be found at https://github.com/exponent-ai/contracts. 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
• Centralization risks
• Trusting trust/dependency vulnerabilities
• Oracle failure/manipulation
• Congestion and scalability
• Consensus failures
• Cryptography problems

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