Sense

Sense is decentralized permissionless infrastructure, where teams can build and develop new yield primitives for DeFi, such as bond-like assets, yield tokens, and tranche-like instruments.

Yield stripping is the first application built atop Sense, where users can lend at a fixed rate and make capital-efficient long/short bets on the future yields of existing yield-bearing assets.

For more information about Sense Finance, please visit https://sense.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 and critical smart contract 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. In addition, all critical bug reports must come with a suggestion for a fix to be considered for a reward.

Known issues highlighted below are considered as out of scope:

• Vulnerabilities involving disabling Space swaps of low-decimal Targets when all liquidity is removed after both sides of the pool have been initialized
• All previously raised issued in the following audit reports:
  • https://github.com/sense-finance/sense-v1/tree/dev/audits
  • https://github.com/sense-finance/space-v1/tree/main/audits

Sense requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a name and an address.

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

Smart Contract

Websites and Applications

All smart contracts of Sense can be found at https://github.com/sense-finance/. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If any Critical or High severity impacts can be caused to any other asset managed by Sense that isn’t on this table but for which the impact is in the Impacts in Scope section, you are encouraged to submit it for the consideration of 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
• Known edge case: disabling Space swaps of low-decimal Targets when all liquidity is removed after both sides of the pool have been initialized

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
• Vulnerabilities primarily caused by browser/plugin defects
• Any vulnerability exploit requiring CSP bypass resulting from a browser bug

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