OpenZeppelin on Stellar
Bounty Range
$1,000 - $25,000
external program
OpenZeppelin on Stellar
Bounty Range
$1,000 - $25,000
external program
As the premier crypto cybersecurity technology and services company, we've built OpenZeppelin Contracts with our best security practices. We are committed to ensuring the utmost security in our community-vetted smart contracts, and our bounty program provides rewards of up to $25,000 USD for reporting critical vulnerabilities in our smart contracts library.
This bug bounty program is focused on OpenZeppelin Stellar Contracts and mainly intends to prevent:
For more information about OpenZeppelin on Stellar, please visit https://docs.openzeppelin.com/stellar-contracts/0.1.0/
OpenZeppelin on Stellar provides rewards in XLM on Stellar, denominated in USD.
Smart Contract
Mainnet assets:
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3. 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 rewards stated here are additive to any existing bug bounty programs hosted by projects that are currently using OpenZeppelin on Stellar contracts.
Bounty rewards are given according to an impact/likelihood matrix for assessing threat levels. Each issue is assessed considering the likelihood of the vulnerability being successfully exploited and the expected impact in scope to a single instance of the affected smart contract. Note that, as can be seen in the matrix, if the impact is Critical then the threat is always Critical, for other impacts the maximum reduction is one level only if the likelihood is low, and if the likelihood is high then the threat is increased one level above the impact.
OpenZeppelin's bug bounty program requires an invoice to be submitted and a KYC screen to be performed prior to OpenZeppelin providing a bug bounty reward. Once a payout is confirmed, a member of OpenZeppelin will reach out to you directly to collect the necessary information, including:
The submission of KYC information is a requirement for payout processing.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
A PoC compliant with Immunefi PoC Guidelines and Rules is required for the following severity levels:
Proof of concept is always required for all severities.
Bugs introduced by a release candidate version and reported during the review period, the dates for which will be declared by OpenZeppelin on each release, will receive a 50% bonus.
OpenZeppelin on Stellar's completed audit reports can be found at https://github.com/OpenZeppelin/stellar-contracts/tree/main/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Category 1: Transparent
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: