Saddle x Immunefi Bug Bounty

Details

Saddle is an automated market maker optimized for trading between pegged value crypto assets.

Further resources regarding the Saddle can be found on their website, https://docs.saddle.finance/.

Rewards by Threat Level

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 Saddle team directly and are denominated in USD. However, payouts are done in USDC.

Smart Contracts and Blockchain

Prioritized Vulnerabilities

Smart Contracts/Blockchain:

• Re-entrancy
• Logic errors: including user authentication errors
• Solidity/EVM details not considered: including integer over-/under-flow and 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

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

The following activities are prohibited by 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
• 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