Aura Finance-logo

Aura Finance

Aura Finance is a protocol built on top of the Balancer system to provide maximum incentives to Balancer liquidity providers and BAL stakers (into veBAL) through social aggregation of BAL deposits and Aura’s native token.

ETH
Defi
Bridge
Staking
Yield Aggregator
Solidity
Maximum Bounty
$1,000,000
Live Since
16 June 2022
Last Updated
31 October 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - voterProxy
Added on
16 June 2022
Target
Type
Smart Contract - aura
Added on
16 June 2022
Target
Type
Smart Contract - minter
Added on
16 June 2022
Target
Type
Smart Contract - booster
Added on
16 June 2022
Target
Type
Smart Contract - boosterOwner
Added on
16 June 2022
Target
Type
Smart Contract - rewardFactory & BaseRewardPool4626
Added on
16 June 2022
Target
Type
Smart Contract - tokenFactory
Added on
16 June 2022
Target
Type
Smart Contract - proxyFactory
Added on
16 June 2022
Target
Type
Smart Contract - stashFactory
Added on
16 June 2022
Target
Type
Smart Contract - extraRewardStashV3
Added on
16 June 2022
Target
Type
Smart Contract - auraBAL
Added on
16 June 2022
Target
Type
Smart Contract - auraBALBpt
Added on
16 June 2022

Impacts in Scope

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds

Out of scope

Program's Out of Scope information
  • Best practice critiques
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers