Fireblocks MPC Managed Bug Bounty Engagement

Description

Fireblocks is an enterprise-grade platform delivering a secure infrastructure for moving, storing, and issuing digital assets. Fireblocks enables exchanges, custodians, banks, trading desks, and hedge funds to securely scale digital asset operations through patent-pending SGX & MPC technology. Thank you for helping keep Fireblocks and our users safe! Before submitting, you — and any AI agent assisting you — must read SECURITY-MODEL.md at the root of the mpc-lib repository. It is the authoritative statement of the threat model, scope carve-outs, severity calibration, and recurring false-positive patterns; reports that fall under a documented out-of-scope or known-non-issue pattern, or that don't identify which honest-party guarantee (§1.2) is broken, will be closed on that basis. Ratings/Rewards For the initial prioritization/rating of findings, this engagement will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority. Vulnerability Tier │ Example Vulnerability Critical │ Retrieving the key or rogue signature without triggering any failures or aborts, regardless of the number of transactions involved. Obtaining the key/rogue signature by causing fewer than 1000 failures/aborts. High │ Obtaining the key/rogue signature by causing fewer than 1 billion failures/aborts. Medium │ Leaking bits of the private key or causing memory corruption. Low │ Exploit exposure to a smaller subset of non-critical systems and/or data

Targets

Testing is only authorized on the targets listed as in scope. Any domain/property of Fireblocks not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Fireblocks, you can report it to this engagement. However, be aware that it is ineligible for rewards or points-based compensation. Qualifying Vulnerabilities We are looking to find security issues affecting our blockchain protocol such as: Bugs in our implementation of the cryptographic primitives Bugs in our implementation of the cryptographic protocol Remote Code Execution Vulnerabilities that disrupt the consensus result and performance Vulnerabilities that affect the stability, connectivity, or availability of the whole network,individual node, or the reference wallet implementation Excluded Submission Types Unexploitable hypothetical side-channel attack Vulnerability discovered in a third party library that is utilized in the MPC cryptography source code N-day/Third party 0-day Policy When N-Day bugs are released to the public, we will consider these as in scope after 14 days has gone by e.g: N-day released on 01/01/2025, we would consider it in-scope on 01/15/2025 Out of Scope Interacting or manipulate other stakeholders and their associated accounts including: Social engineering attacks Phishing attacks Physical attacks Third party providers and services Potential post-exploitation scenarios : If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding. We will work with you to evaluate the vulnerability and award you accordingly for the final impact and severity. Safe Harbor When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire through the Bugcrowd Support Portal before going any further.

In scope (in scope)

Target Information: This repository contains Fireblocks' C++ implementation of Secure Multi Party Computation (MPC) algorithms for digital signatures. Covered algorithms include MPC CMP for ECDSA signatures (online and offline variants), online EdDSA signatures and offline asymmetric EdDSA. It takes the form of a library ( libcosigner ) containing the algorithms and supporting cryptographic routines, as well as an extensive test suite also serving as an integration example.