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.

Ola Finance is not another lending protocol like Compound or Aave. Rather, Ola is a service provider that brings the lending infrastructure and expertise needed to deploy and scale Compound-like instances. Each network, governed and controlled by the creator, presents a variety of benefits.

For more information about Ola Finance, please visit https://ola.finance/.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical severity vulnerabilities will only be considered Critical if they could potentially cause at least USD 50 000 in economic damage. All vulnerabilities that would have been classified as Critical but have an economic impact of less than USD 50 000 will be downgraded to a lower severity at the discretion of the protocol.

Known issues highlighted in the following audit reports are considered out of scope:

• Solidified (Oct 11, 2021): https://drive.google.com/file/d/1NbJNRIYwIZ7uDxB6sXDUYwH38EYMa5JB/view
• Solidified (May 18, 2022): https://drive.google.com/file/d/1Rpuaxm5xxZAZWRxPWjYE6_bxVbPNcwJz/view

Payouts are handled by the Ola Finance team directly and are denominated in USD. However, payouts are done in USDC.

For proxy contracts, only the current implementation and any further updates to the implementation contracts are considered in scope.

If any Critical/High severity impact can be caused to any other asset managed by Ola Finance that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

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)

Smart Contracts and Blockchain

• 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
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• 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
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this 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 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty