CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
MiSon Protocol logo
MiSon Protocol
Asset Management
DeFi
AI
Max Payout
$5,000
Project Overview

MiSon Protocol enhances decentralized finance through an advanced "Oracle + Radar" pre-authorization system that rigorously screens projects based on predefined conditions and indicators. By assessing liquidity provision risks and rewards, MiSon focuses on sustainable fund management and optimized investment strategies to mitigate risks while maximizing returns for users.

Rewards by Severity

Program Overview The Mison Protocol Bug Bounty Program invites security researchers and ethical hackers to identify vulnerabilities within the Mison ecosystem. As part of its ongoing security commitment, Mison Protocol seeks to ensure the reliability and robustness of its smart contracts and supporting infrastructure through community-driven audits and responsible disclosures.

Reward Structure All valid submissions are evaluated using a 4-tier severity model, with rewards based on the criticality of the vulnerability and its potential impact. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, considering the funds affected and potential reputational risks at the time of report submission. High-severity vulnerabilities may receive up to 100% of the funds at risk, subject to team evaluation.

Submission Requirements Bug reports must include a working proof of concept (PoC) and detailed reproduction steps that demonstrate the real impact on an asset in scope. Submissions consisting only of written explanations or hypothetical scenarios will not qualify for rewards.

Payouts All validated rewards will be paid in MI, the native token of Mison Protocol.

Smart Contract
Web Application
Blockchain
The bounty will be paid out in MI
Assets In-Scope
Target
Severity
Name
https://github.com/MiSon-Protocol
Smart Contract
MI/USDT
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of any user funds - whether at-rest or in-motion - other than unclaimed yield
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Double spending
Protocol insolvency
Major
Faulty usage of proxy patterns
Temporary denial of services
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
Low
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value. Missing events for functions that change critical parameters
Web Application
Critical
Non-intuitive return values
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Major
Remote code execution and code injection
SQL injection
Obtaining high-impact sensitive information from the internal system
XXE/XML injection vulnerability with high-security impact
Authentication and authorization bypass with high impact
Wormable stored XSS
Large scale account takeover
Leakage of a lot of source code
Medium
Stored XSS on general pages
CSRF involving core business; etc
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Medium impact information disclose
Low
Reflected XSS - DOM XSS and Flash-based XSS
No return value and no in-depth utilization of successful SSRF
Other vulnerabilities with low-security impact
Blockchain
Critical
Network not being able to confirm new transactions (Total network shutdown)
Transaction/consensus manipulation
Unauthorized token minting
Problems and safety hazards that arise during the operation process
Major
Transient consensus failures
Bad/incorrect usage of cryptography primitives
Important safety hazards and issues
Medium
Vulnerability in RPC API (except via DDoS attack)
Attacks against thin clients
Unhandled on-chain errors affecting a user corner case
Low
Common operational issues and hidden dangers
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Sybil attacks
Centralization risks
Web Application
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Missing best practices in SSL/TLS configuration
Issues that require unlikely user interaction
Non-Sensitive Data Disclosure - for example server version banners
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
Missing HttpOnly or Secure flags on cookies
Presence of autocomplete attribute on web forms
Blockchain
Centralization risks
Best practice critiques
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward. Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact. When duplicates occur we only award the first report that was received (provided that it can be fully reproduced). Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder. Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services. Do not attempt to perform brute-force attacks or denial-of-service attacks. Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Any testing with mainnet or public testnet contracts - all testing should be done on private testnets. Automated testing of services that generate significant amounts of traffic. Public disclosure of an unpatched vulnerability in an embargoed bounty. Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceJul 3, 2024
Last Updated5mo 15d ago
Funds Reserved$300,000
Max Payout$5,000
Skynet Score
78.65
BBB
KYC
Required
PoC
Required
View on Skynet