Audit Comp | Lido: Mellow Vault-logo

Audit Comp | Lido: Mellow Vault

Mellow Decentralized Validator Vault

ETH
Defi
DAO
Liquid Staking
Staking
Solidity

Status

Finished
Rewards Pool
$100,000
Vault TVL
$18,500
Started
15 August 2024
Ended
05 September 2024
Rewards Token
DAI
nSLOC
1,281
  • Triaged by Immunefi

  • PoC required

  • Vault program

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - Vault.sol - 454
Added on
15 August 2024
Target
Type
Smart Contract - VaultConfigurator.sol - 365
Added on
15 August 2024
Target
Type
Smart Contract - ERC20TvlModule.sol - 15
Added on
15 August 2024
Target
Type
Smart Contract - StakingModule.sol - 77
Added on
15 August 2024
Target
Type
Smart Contract - ChainlinkOracle.sol - 65
Added on
15 August 2024
Target
Type
Smart Contract - ConstantAggregatorV3.sol - 12
Added on
15 August 2024
Target
Type
Smart Contract - ManagedRatiosOracle.sol - 30
Added on
15 August 2024
Target
Type
Smart Contract - WStethRatiosAggregatorV3.sol - 16
Added on
15 August 2024
Target
Type
Smart Contract - DefaultProxyImplementation.sol - 12
Added on
15 August 2024
Target
Type
Smart Contract - Initializer.sol - 25
Added on
15 August 2024
Target
Type
Smart Contract - SimpleDVTStakingStrategy.sol - 57
Added on
15 August 2024
Target
Type
Smart Contract - ManagedValidator.sol - 96
Added on
15 August 2024

Impacts in Scope

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Eligibility Criteria

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

  • On OFACs SDN list
  • Official contributor, both past or present
  • Employees and/or individuals closely associated with the project
  • Security auditors that directly or indirectly participated in the audit review

Responsible Publication

Whitehats may publish their bug reports after they have been fixed & paid, or closed as invalid, with the following exceptions:

  • Bug reports in mediation may not be published until mediation has concluded and the bug report is resolved.

Immunefi may publish bug reports submitted to this audit competition and a leaderboard of the participants and their earnings.

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

Immunefi Standard Badge

By adhering to Immunefi’s best practice recommendations, Ionic has satisfied the requirements for the Immunefi Standard Badge.

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

Severity
Critical
Title

Protocol insolvency

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Theft of unclaimed royalties

Severity
High
Title

Permanent freezing of unclaimed yield

Severity
High
Title

Permanent freezing of unclaimed royalties

Severity
High
Title

Temporary freezing of funds for at least 1 week

Severity
Medium
Title

Smart contract unable to operate due to lack of token funds

Severity
Medium
Title

Block stuffing

Severity
Medium
Title

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Severity
Medium
Title

Theft of gas

Out of scope

Program's Out of Scope information

These impacts are out of scope for this bug bounty program.

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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
  • 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

Blockchain/DLT & 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

Prohibited Activities:

  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty