DeFi Saver-logo

DeFi Saver

DeFi Saver is an advanced management app for decentralized finance protocols such as MakerDAO, Compound, Aave and Reflexer, with a special focus on creating and managing leveraged positions.

ETH
Defi
Asset Management
Solidity
Maximum Bounty
$350,000
Live Since
21 April 2021
Last Updated
24 September 2025
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Target
Type
Websites and Applications
Added on
13 May 2022
Target
Type
Smart Contract - Defi Saver V3 (excluding the 'mocks' and 'views' folders)
Added on
24 September 2025

Impacts in Scope

Severity
Critical
Title

Any governance voting result manipulation

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

Miner-extractable value (MEV)

Severity
Critical
Title

Protocol insolvency

Severity
Critical
Title

Ability to execute system commands

Severity
Critical
Title

Extract Sensitive data/files from the server such as /etc/passwd

Severity
Critical
Title

Taking down the application/website

Severity
Critical
Title

Stealing User Cookies

Severity
Critical
Title

Bypassing Authentication

Severity
Critical
Title

Signing transactions for other users

Severity
Critical
Title

Redirection of user deposits and withdrawals

Out of scope

Program's Out of Scope information
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization
  • Feature requests
  • Best practice critiques
  • Customer support pop-up (aka Helpcrunch integration)
Default Out of Scope and rules

Web & App specific

  • Theoretical impacts without any proof or demonstration
  • Impacts involving attacks requiring physical access to the victim device
  • Impacts involving attacks requiring access to the local network of the victim
  • Reflected plain text injection (e.g. url parameters, path, etc.)
    • This does not exclude reflected HTML injection with or without JavaScript
    • This does not exclude persistent plain text injection
  • Any impacts involving self-XSS
  • Captcha bypass using OCR without impact demonstration
  • CSRF with no state modifying security impact (e.g. logout CSRF)
  • Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
  • Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
  • Impacts causing only the enumeration or confirmation of the existence of users or tenants
  • Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
  • Lack of SSL/TLS best practices
  • Impacts that only require DDoS
  • UX and UI impacts that do not materially disrupt use of the platform
  • Impacts primarily caused by browser/plugin defects
  • Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
  • Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
  • SPF/DMARC misconfigured records)
  • Missing HTTP Headers without demonstrated impact
  • Automated scanner reports without demonstrated impact
  • UI/UX best practice recommendations
  • Non-future-proof NFT rendering

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