Longdrink Finance

Submit a Bug
24 August 2021
Live since
No
KYC required
$25,000
Maximum bounty

Program Overview

Longdrink Finance is a decentralized and autonomous asset manager creating index tokens on the Binance Smart Chain. Members can diversify their asset exposure by trading indices, decide on new products and participate in the platform’s development through holding the $LONG governance token. Longdrink Finance’s ambition is to create a community-governed Blackrock in the DeFi world, powered by its large group of members rather than a chosen few investment analysts.

By providing these instruments, Longdrink Finance aims to enable exposure to the wider cryptocurrency market to those who are interested in the sector but do not have the time or inclination to research which projects are worthy of their attention, or separate the signals from the noise in the wider market (synonymous to the fittingly called cocktail effect). They are intended to act as 'set and forgets' for the more passive investor.

For more information about Longdrink Finance, please visit https://longdrink.finance/.

This bug bounty program is focused on their smart contracts, website, and application, and is focused on preventing the following impacts:

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Theft of governance funds
  • Theft of unclaimed yield
  • Temporary freezing of funds
  • Unable to call smart contract
  • Smart contract gas drainage
  • Smart contract fails to deliver promised return
  • Redirected funds by address modification
  • Injection of text
  • Users spoofing other users
  • Shell access on server

Rewards by Threat Level

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/app bug reports must come with a PoC in order to be considered for a reward.

Any vulnerability already reported on previous audits, including these Medium-level issues, that has not been patched is not in-scope of the bug bounty program.

Payouts are handled by the Longdrink Finance team directly and are denominated in USD. However, payouts are done in USDC, USDT, BNB, or ETH, at the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
USD $25,000
Payout
high
Level
USD $10,000
Payout
medium
Level
USD $2,500
Payout
low
Level
USD $500
Payout

Web and Apps

Critical
Level
USD $25,000
Payout
high
Level
USD $10,000
Payout
medium
Level
USD $2,500
Payout
low
Level
USD $500
Payout

Assets in Scope

Further information about the smart contracts in Longdrink Finance can be found at https://github.com/LongdrinkDefi. However, only those in the assets in scope table are considered as in-scope of the bug bounty program.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Theft of governance funds
  • Theft of unclaimed yield
  • Temporary freezing of funds
  • Unable to call smart contract
  • Smart contract gas drainage
  • Smart contract fails to deliver promised return

Web/App

  • Redirected funds by address modification
  • Injection of text
  • Users spoofing other users
  • Shell access on server

Prioritized Vulnerabilities

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

Smart Contracts and Blockchain

  • Re-entrancy
  • Logic errors
    • including user authentication errors
  • Solidity/EVM details not considered
    • including integer over-/under-flow
    • including rounding errors
    • including unhandled exceptions
  • Trusting trust/dependency vulnerabilities
    • including composability vulnerabilities
  • Oracle failure/manipulation
  • Novel governance attacks
  • Economic/financial attacks
    • including flash loan attacks
  • Congestion and scalability
    • including running out of gas
    • including block stuffing
    • including susceptibility to frontrunning
  • Consensus failures
  • Cryptography problems
    • Signature malleability
    • Susceptibility to replay attacks
    • Weak randomness
    • Weak encryption
  • Susceptibility to block timestamp manipulation
  • Missing access controls / unprotected internal or debugging interfaces

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)

Out of Scope & Rules

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

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