FIBOS Security-vulnerabilities and Threat-intelligence Bounty Programme

HOME 中文
Table of Contents
Content

Scope of Business

FIBOS mainnet, source code: https://github.com/fibosio

Processing Flow

Reporting Stage

The reporter visits "SlowMist Zone" website and goes to "Submit Bug Bounty" (URL:https://slowmist.io/en/bug-bounty.html) to submit a threat intelligence. (Status: to be review)

Processing Stage

1. Within one working day, the SlowMist Security Team will confirm the threat intelligence report from the "SlowMist Zone", follow up, evaluate the problem, and feed the intelligence back to the FIBOS contact person in the meantime (status: under review).

2. Within three working days, the FIBOS technical team will deal with the problem, draw conclusions and record points (status: confirmed / ignored). They will communicate with the reporter if necessary, and ask the reporter for assistance.

Repairing Stage

1. The FIBOS business department shall repair the security problems in the threat intelligence and update online (status: repaired). The repairing timeframe depends on the problem severity and the repair difficulty. Generally speaking, it is within 24 hours for the critical and high-risk problems, within 3 working days for the medium-risk problems, and within 7 working days for the low-risk problems. The App security issue is limited by the version release, and the repairing timeframe is on a case-by-case basis.

2. The reporter will review whether the security problem has been repaired (Status: reviewed/reviewed with objection).

3. After the reporter confirms that the security problem is repaired, the FIBOS technical team will inform the SlowMist Security Team of the conclusion and the vulnerability score. They will issue rewards with the SlowMist Security Team (status: completed).

Vulnerability Level and Reward Standards

Level FIBOS Reward SlowMist Zone Reward*
Critical 100,000 FO 512 SLOWMIST
High 50,000 FO 256 SLOWMIST
Medium 20,000 FO 100 SLOWMIST
Low 5,000 FO 32 SLOWMIST

*Remark: the final award depends on the severity of the vulnerability and the true impact of the vulnerability, the values in the table are the highest rewards for each level. If the FO/EOS price fluctuates significantly, it will be adjusted according to the actual situation.

*SLOWMIST is Ethereum ERC20 Token, the ecological incentive token for the SlowMist Zone.

Critical Vulnerabilities

A critical vulnerability refers to the vulnerability occurs in the core business system (underlying virtual machine, wallet, etc.), it can cause a severe impact.

It is including but not limited to:

High-risk Vulnerabilities

Medium-risk Vulnerabilities

Low-risk Vulnerabilities

Vulnerabilities that are not accepted at the moment (even if such a vulnerability is submitted, it will be ignored)

Special thanks to The xianzhi vulnerability classification criteria referred here.