Coreum

Coreum addresses the existing limitations of the current blockchains and empowers a solid foundation for future decentralized projects. Coreum’s unique approach is to provide built-in, on-chain solutions to process transactions in a deterministic way to ensure a fast, secure, cheap, and green network for various use cases.

For more information about Coreum, please visit https://www.coreum.com/

Coreum provides rewards in COREUM. For more details about the payment process, please view the Rewards by Threat Level section further below.

Responsible Publication

Coreum adheres to category 3: Approval Required. This Policy determines what information whitehats 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

Coreum adheres to the Primacy of Impact for their entire program If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.

Testnet and mock files are not covered under the Primacy of Impact.

All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

Known Issue Assurance

Coreum commits to providing Known Issue Assurance to bug submissions through their program. This means that Coreum will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.

Immunefi Standard Badge

Coreum has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 25 000, but may also consider subsequent impacts on other projects built on the respective blockchain, as well as PR and brand reputation risk, capped at the maximum critical reward USD 25 000.

To incentivize security researchers and ensure bug reports are not withheld, a minimum reward USD 3 000 will be provided.

For Total Network Shutdown, the maximum payment of 25 000 will be rewarded.

Repeatable Attack Limitations

If the blockchain/DLT component where the vulnerability exists can be upgraded/paused/killed, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading, pausing, or in some cases, killing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.

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

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program.

• Previously known vulnerabilities in Tendermint(CometBFT) and or/any other fork of these.
• Previously known vulnerabilities in Cosmos-SDK and or/any other fork of these.
• Previously known vulnerabilities in CosmWasm and or/any other fork of these.
• Previously known vulnerabilities in IBC and or/any other fork of these.
• Any other vulnerabilities that come from Third-Party services and SDKs.
• Public Zero-day vulnerabilities
• Any issue on the issue tracker: https://github.com/CoreumFoundation/coreum/issues
• Any issue found on open pull requests: https://github.com/CoreumFoundation/coreum/pulls
  • The bridge is out of scope - Coreum to XRPL and XRPL to Coreum

Previous Audits

Coreum has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

• https://skynet.certik.com/projects/coreum

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Blockchain/DLT - Critical
• Blockchain/DLT - High
• Blockchain/DLT - Medium
• Blockchain/DLT - Low

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Other Terms and Information

Payouts are handled by the Coreum team directly and are denominated in USD. However, payouts are done in COREUM. This bug bounty program will have a hard cap of USD 500 000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis.

Reward Payment Terms

Payouts are handled by the Coreum team directly and are denominated in USD. However, payments are done in COREUM.

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. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.

All code of Coreum can be found at https://github.com/orgs/CoreumFoundation/repositories. Documentation for the assets provided in the table can be found at https://docs.coreum.dev/overview/introduction.html.

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about Reported Subdomain Takeovers.

Other helpful links include:

• Coreum documentation and tutorials - https://docs.coreum.dev
• Coreum smart tokens - https://docs.coreum.dev/tutorials/smart-tokens/main.html
• Coreum code examples - https://github.com/CoreumFoundation/tutorials

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

Smart Contracts and Blockchain/DLT

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Impacts requiring basic economic and governance attacks (e.g. 51% attack)
• Lack of liquidity impacts
• Impacts from Sybil attacks
• Impacts involving centralization risks
• Best practice recommendations

The following activities are prohibited by this bug bounty program:

• 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
• Phishing attacks or scams
• Previously known vulnerabilities in Tendermint(CometBFT) and or/any other fork of these.
• Previously known vulnerabilities in Cosmos-SDK and or/any other fork of these.
• Previously known vulnerabilities in CosmWasm and or/any other fork of these.
• Previously known vulnerabilities in IBC and or/any other fork of these.
• Any other vulnerabilities that come from Third-Party services and SDKs.
• Public Zero-day vulnerabilities
• Denial of service (DoS) / Distributed Denial of Service(DDOS) / Spamming
• Email services configuration DKIM and SPF records.
• Any issue on the issue tracker: https://github.com/CoreumFoundation/coreum/issues
• Any issue found on open pull requests: https://github.com/CoreumFoundation/coreum/pulls
  • The bridge is out of scope