Saffron Finance

Saffron Finance is a decentralized protocol that acts as a yield optimizer for liquidity providers – it was first announced through a Medium article by a group of anonymous developers and was later launched on the Ethereum main net on 1 November 2020. Liquidity pools in Saffron Finance collect deposited base assets from liquidity providers and deploy them onto lending platforms to earn interest. However, unlike other yield aggregators, Saffron Finance aims to differentiate itself through the introduction of tranches.

One of the biggest issues that yield farming pools face is the effects of impermanent loss. Liquidity providers may lose out on value when the market price of their deposited assets is lower than when it was initially deposited. Through tranches, Saffron Finance aims to provide better exposure to yield farmers and give them the option to select portfolios based on their preferred risk appetite.

Saffron Finance acts as an intermediary between liquidity providers and lending protocols. Through adaptors, the Saffron Finance protocol will automatically deploy its liquidity pools to the highest-yielding lending protocol at a given interval. Liquidity providers may supply Saffron Finance’s liquidity pools at any given time but are only able to withdraw their assets and interest earnings at the end of every epoch. Each epoch lasts for 2 weeks.

The bug bounty program covers its web app and is focused on Web3 / javascript exploits or vulnerabilities that can cause an attack on metamask and users’ data or funds.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

The bug bounty program for web/app bugs covers only client-side vulnerabilities in the app as loaded by the browser. This excludes any vulnerabilities affecting CDNs, servers, DNS, or other project-controlled infrastructure.

Payouts are handled by the Saffron Finance team directly and are denominated in USD. Payouts are done in USDC.

Only web/app vulnerabilities that directly affect the web/app assets listed in this table are accepted within the bug bounty program. All others are out-of-scope.

The bug bounty program for the assets in scope in this table covers only client-side vulnerabilities in the app as loaded by the browser. This excludes any vulnerabilities affecting CDNs, servers, DNS, or other project-controlled infrastructure.

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

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)

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by 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