SynFutures Vault

Triaged by Immunefi

Submit a Bug
09 May 2024
Live since
Yes
KYC required
$10,000
Maximum bounty
09 May 2024
Last updated

VaultImmunefi vault program

This project deposits assets in a decentralized vault to publicly show proof of assets for paying out bug bounty rewards on-chain via the Immunefi dashboard

VaultPublic vault address
0xAce31615e91aBBB55C993C214b03c4eCe61fEbA5
VaultFunds available
$0
Vault30d Avg. Funds availability
$233.33
VaultAssets in vault

    Program Overview

    SynFutures is a decentralized perpetual futures protocol, facilitating open and transparent trading on any assets and listings instantly. The V3 Oyster AMM launched the industry first-ever unified AMM and on-chain order book model.

    For more information about SynFutures, please visit https://www.synfutures.com/

    SynFutures provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.

    KYC Requirement

    SynFutures will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

    • Full name
    • Date of birth
    • Proof of address (either a redacted bank statement with address or a recent utility bill)
    • Copy of Passport or other Government issued ID

    Eligibility Criteria

    Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

    • On OFACs SDN list
    • Official contributor, both past or present
    • Employees and/or individuals closely associated with the project
    • Security auditors that directly or indirectly participated in the audit review

    Responsible Publication

    SynFutures adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

    Primacy of Impact vs Primacy of Rules

    SynFutures adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.

    Proof of Concept (PoC) Requirements

    A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

    Known Issue Assurance

    SynFutures commits to providing Known Issue Assurance to bug submissions through their program. This means that SynFutures will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission.

    In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.

    Previous Audits

    SynFutures’s completed audit reports can be found at https://www.synfutures.com/Quantstamp-Audit-Report-SynFuturesV3.pdf. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

    Feasibility Limitations

    The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

    Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

    Immunefi Standard Badge

    By adhering to Immunefi’s best practice recommendations, SynFutures has satisfied the requirements for the Immunefi Standard Badge.

    Rewards by Threat Level

    Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

    Reward Calculation for Critical Level Reports

    For critical web/apps bug reports will be rewarded with USD 10 000, only if the impact leads to:

    • A loss of funds involving an attack that does not require any user action
    • Private key or private key generation leakage leading to unauthorized access to user funds

    All other impacts that would be classified as Critical would be rewarded a flat amount of USD 5 000. The rest of the severity levels are paid out according to the Impact in Scope table.

    Reward Payment Terms

    Payouts are handled by the SynFutures team directly and are denominated in USD. However, payments are done in USDC on Ethereum.

    The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

    Websites and Applications

    Critical
    Level
    USD $6,000 to USD $10,000
    Payout
    PoC Required
    High
    Level
    USD $5,000
    Payout
    PoC Required
    Medium
    Level
    USD $2,000
    Payout
    PoC Required
    Low
    Level
    USD $1,000
    Payout
    PoC Required

    Assets in scope

    SynFutures’ codebase can be found at https://github.com/SynFutures/. Documentation and further resources can be found on https://docs.synfutures.com/.

    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.

    Websites and Applications

    • Execute arbitrary system commands
      Critical
      Impact
    • Retrieve sensitive data/files from a running server, such as: /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
      Critical
      Impact
    • Taking down the application/website
      Critical
      Impact
    • Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.
      Critical
      Impact
    • Subdomain takeover with already-connected wallet interaction
      Critical
      Impact
    • Direct theft of user funds
      Critical
      Impact
    • Malicious interactions with an already-connected wallet, such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions
      Critical
      Impact
    • Injection of malicious HTML or XSS through metadata
      Critical
      Impact
    • Injecting/modifying the static content on the target application without JavaScript (persistent), such as: HTML injection without JavaScript, Replacing existing text with arbitrary text, Arbitrary file uploads, etc
      High
      Impact
    • Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Email, Password of the victim etc.
      High
      Impact
    • Improperly disclosing confidential user information, such as: Email address, Phone number, Physical address, etc.
      High
      Impact
    • Subdomain takeover without already-connected wallet interaction
      High
      Impact
    • Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Changing the name of user, Enabling/disabling notifications
      Medium
      Impact
    • Injecting/modifying the static content on the target application without JavaScript (reflected), such as: Reflected HTML injection, Loading external site data
      Medium
      Impact
    • Redirecting users to malicious websites (open redirect)
      Medium
      Impact
    • Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction, such as: Iframing leading to modifying the backend/browser state (demonstrate impact with PoC)
      Low
      Impact
    • Taking over broken or expired outgoing links, such as: Social media handles, etc.
      Low
      Impact
    • Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.
      Low
      Impact

    Out of Scope & Rules

    These impacts are out of scope for this bug bounty program.

    All Categories:

    • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
    • Impacts caused by attacks requiring access to leaked keys/credentials
    • Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
    • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
    • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
    • Best practice recommendations
    • Feature requests
    • Impacts on test files and configuration files unless stated otherwise in the bug bounty program

    Websites and Apps

    • Theoretical impacts without any proof or demonstration
    • Impacts involving attacks requiring physical access to the victim device
    • Impacts involving attacks requiring access to the local network of the victim
    • Reflected plain text injection (e.g. url parameters, path, etc.)
      • This does not exclude reflected HTML injection with or without JavaScript
      • This does not exclude persistent plain text injection
    • Any impacts involving self-XSS
    • Captcha bypass using OCR without impact demonstration
    • CSRF with no state modifying security impact (e.g. logout CSRF)
    • Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
    • Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
    • Impacts causing only the enumeration or confirmation of the existence of users or tenants
    • Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
    • Lack of SSL/TLS best practices
    • Impacts that only require DDoS
    • UX and UI impacts that do not materially disrupt use of the platform
    • Impacts primarily caused by browser/plugin defects
    • Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
    • Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
    • SPF/DMARC misconfigured records)
    • Missing HTTP Headers without demonstrated impact
    • Automated scanner reports without demonstrated impact
    • UI/UX best practice recommendations
    • Non-future-proof NFT rendering

    Prohibited Activities:

    • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
    • 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 that are executed against project assets
    • Automated testing of services that generates significant amounts of traffic
    • Public disclosure of an unpatched vulnerability in an embargoed bounty