Aspen Labs

Aspen Labs is decentralized application company. Within the framework of their first roadmap they are engaged in constructing the Hypersphere, a single-pool, cross-chain decentralized exchange. dLEND, their social finance application allows digital asset holders to lend to qualified home owners and students. And finally dCOLLECT, an NFT marketplace and auction host for historical moments.

The Aspen Labs team possesses a long history of involvement with the blockchain and finance environments. They are committed to creating products and applications that facilitate the growth and usability of blockchain for every user.

For more information about Aspen Labs, please visit https://www.aspenlabs.io/.

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

• Thefts or freezing of funds of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Website goes down
• Inaccurate displays of data between smart contracts and user interface
• Inaccurate calculation of rewards
• Text injections
• Website phishing redirects

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. A PoC is also required for Critical and High Smart Contract/Blockchain bug reports.

Theft of Yield greater than the equivalent of USD 100 000 is considered critical.

Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum of USD 75 000 for Critical bug reports.

Payouts are handled by the Aspen Labs team directly and are denominated in USD. However, payouts over USD 1 000 are done in ASPEN. However, payouts that are less than or equal to USD 1 000 are done in a stablecoin at the choice of the team.

All smart contracts of Aspen Labs can be found at https://github.com/AspenLab. 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/Blockchain

• Issues concerning the exploitation of pool asset balances that cause loss of funds
• Loss of users funds staked (principal) by freezing or theft
• Theft of yield
• Freezing of unclaimed yield
• Temporary freezing of fund for minimum 20 minutes
• Unable to call smart contract
• Smart contract fails to deliver promised returns
• Differences between displayed data and actual returns
• NFT staking contract miscalculation of yields (ie. weight errors in contract)
• Non-Aspen NFTs being able to be staked in NFT staking contract
• Accurate calculation of rewards in both the Hypersphere exchange and NFT staking

Web/App

• Site goes down
• Redirection of pages to phishing urls
• Injection of text

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)

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