Ola Finance
Ola Finance allows anyone to create their own white-labeled lending network through a unique Lending-as-a-Service offering. Each network is highly customizable, from tunable parameters to supported tokens. Once deployed, Ola offers ongoing maintenance, risk advisory, and custom feature support to help grow the network while allowing the creator the autonomy to focus on their core product.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency resulting in unpaid debts
Execute arbitrary system commands that cause loss of funds
Direct theft of user funds
Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
Temporary freezing of funds for at least 24 hours
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.
Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data
Taking down the application/website for more than 48 hours
Subdomain takeover with already-connected wallet interaction
Out of scope
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Best practice critiques
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