XBE Finance

XBE is a protocol for DeFi, the man on the street, and even the man on wall street. Integrated Finance allows you to earn in DeFi no matter where you come from, so you can get more out of your FIAT, your securities portfolio, and even your DeFi instruments.

XBE has set out to integrate the functions of Financial Securities, FIAT services, and Decentralised Finance in a complementary protocol that brings the best of the three worlds together

The core product being The XBE Hive, is a yield complementary program built on top of Curve and Convex which allows for people and protocols to earn amplified yield on their Curve Liquidity. XBE does not accumulate the underlying $CRV and $CVX but rather passes this onto to the protocol users

For more information about XBE Finance, please visit https://xbe.finance/.

This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:

• Loss of users funds
• Loss of treasury funds
• Any governance voting result manipulation
• Novel governance attacks
• Economic/Financial attacks (Including flash loan attacks)
• Any freezing of funds

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. 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 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 bug reports must come with a suggestion for a fix in order to be considered for a reward.

Known issues previously highlighted in the following audits are considered as out of scope:

• https://github.com/XBEfinance/audits

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

Smart Contract

Websites and Applications

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

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