SharedStake

Submit a Bug
15 April 2021
Live since
No
KYC required
$1,000,000
Maximum bounty

Program Overview

SharedStake is an initial custodial staking service that allows anyone to stake their ETH without having to maintain or monitor validator nodes. Simply put, SharedStake removes friction associated with ETH 2 staking:

  • Any amount of ETH can be staked by pooling on SharedStake
  • The validators are run on AWS, one of the best cloud providers with industry-leading uptimes
  • Thanks to our derivative staking token, vETH2, we are able to create a liquid market to allow participants to exit their positions or leverage DeFi apps, even before Ethereum 2 launches

For more information about SharedStake, please visit

https://docs.sharedstake.org.

The bug bounty program is focused around its smart contracts and the prevention of loss of user funds and arbitrage/flash loan attacks.

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.

The final reward amount for critical vulnerabilities is capped at 10% of the economic damage based on the vulnerability reported with a payout floor of USD 50 000.

All web and app bug reports must come with a Proof of Concept (PoC) showing impact. Reports without a PoC will be automatically rejected.

Payouts are handled by the SharedStake team directly and are denominated in USD. Payouts are done in SGT.

Smart Contracts and Blockchain

Critical
Level
Up to USD $1,000,000
Payout
high
Level
USD $5,000
Payout
medium
Level
USD $500
Payout
low
Level
USD $250
Payout
none
Level
USD $0
Payout

Web and Apps

Critical
Level
USD $500
Payout
high
Level
USD $250
Payout
medium
Level
USD $100
Payout

Assets in Scope

Prioritized Vulnerabilities

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

Smart Contracts/Blockchain:

  • Re-entrancy
  • Logic errors
    • including user authentication errors
  • Solidity/EVM details not considered
    • including integer over-/under-flow
    • 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
  • Internal SSRF
  • Session fixation
  • Insecure Deserialization
  • Direct object reference
  • DOM XSS
  • SSL misconfigurations
  • SSL/TLS issues (weak crypto, improper setup)
  • URL redirect
  • Clickjacking (must include PoC to be considered)
  • 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
  • Requests for new features

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