Flux Bug Bounty Program

The Flux Community and Foundation are happy to announce –“ The Flux Bug Bounty Program ” to reward security researchers and developers who invest their time and effort in finding bugs or exploits and reporting them through the attached procedure for responsible disclosure of qualifying security vulnerabilities. Please, contribute to our code! – Daniel Keller CSO

What can you earn?

All bugs will be evaluated according to the CVSS scoring scale and rewarded accordingly. The CVSS levels are:

Base level rewards are:

None: 100 Flux for purely cosmetic bugs
Low: 250 Flux for low order bugs.
Medium: 250-1000 Flux
High: 1000-3000 Flux
Critical: 3000-5000 Flux

Bounties are set and paid in Flux only!

For High and Critical level bugs, there are multipliers for incentivized exploits, Coin destructive exploits as well as chain splitting or halting exploits. However, the exact nature of these multipliers will not be disclosed publicly. So, if you do happen to have something of that nature, please do reach out and we will make accommodations.

Responsible Disclosure Policy

To encourage responsible disclosure, no legal action shall be taken against you, provided you adhere to the following points:

1 For Zelcore related issues: Exploits and bugs are restricted to your own account or instance of the Zelcore wallet and have been carried out for validation purposes only.

2For website related issues: No data is removed from the website upon discovery.

3The Flux Blockchain and nodes: Any and all exploits be confined to a private testnet or regtest for validation purposes. Any code modifications carried out to run exploits need to be disclosed along with the effects for full validation.

4For the FluxOS distributed operating system, any and all exploits are confined to their own nodes for validation purposes. Should additional nodes be required to fully validate more serious exploits, the Flux team will assist with a private testnet.

5Submissions can only be made to [email protected] or via direct message to a developer on Discord in either case using the attached PGP keys for encryption is a requirement.

6Include an email for responses in your report.

7Adhere to timeframes laid out in initial confirmation of report emails.

How it works:

AAdhere to the Responsible Disclosure Policy

BMake all possible effort to not interrupt or degrade our service.

CDo not attempt to gain unauthorized access to user accounts, assets or information (use your own account/accounts to test against).

DDo not copy or modify any files or data, including permissions, and do not intentionally view or access any data beyond what is needed to prove the vulnerability.

EDo not exploit a security issue you discover beyond the point of validation on own accounts/nodes.

FWe publish a list of researchers who have submitted valid security reports.

GHowever, should you wish to remain anonymous, we will respect your privacy.

HWe reserve the right to determine timeframes for publishing reports (and accompanying updates) pertaining to each instance. However, we will provide best effort information to you on all such issues.

Eligibility Requirements

We have the right to remove you from the Bug Bounty Program and disqualify you from receiving any bounty rewards if you: Are in violation of any national, state, or local law or regulation

Scope of Services covered by the programme:

(Apps): ZelCore (Win/Linux/MacOS X) – must be on the latest/recent update (released in the last 30 days)

(Mobile): ZelCore Mobile – latest available release on Google Play store and Apple App store

(Libraries): zeltrezjs library

(Website): zel.network, my.zel.cash

(Email): @zel.network, @zel.cash

(Open Source): Flux/Fluxnode Daemon, Flux, Zel-ID, etc.

(Infrastructure): FluxCore explorers & other servers hosted by Flux Team

Out-of-scope Service

Third-party libraries

Infrastructure not managed by Flux Teams such as Public Explorers and FluxNodes run by community members

Qualifying Bugs

1 Injection flaws such as SQL, noQSL, Mongodb, OS injection that tricks command interpreter into executing unintended commands without proper authorization.

2Broken authentication/session management that allows compromise of passwords, keys, or session tokens

3Sensitive data exposure due to improper protection of data via insecure API or flaw in cryptography implementation3

5Cross-Site Request Forgery (CSRF) for sensitive functions in a privileged context

6Remote code execution (RCE)

7Insecure Direct Object References

8Privilege Escalation

9Significant Security Misconfiguration (when not caused by user)

10Directory Traversal

11Open Redirects

12Spoofing enablement

13Any significant abuse-related methodologies that could lead to significant harm The above list is by no means exhaustive, so if you have a bug not on it but not on the excluded list, do reach out, it is covered.

Non-Qualifying Bugs

1Non-original or previously disclosed/reported bugs (with fixes currently underway).

2Non-technical attacks such as social engineering, phishing, or physical attacks against entities or infrastructure.

3Any degrading/damaging the reliability or integrity of our services (such as DDoS attacks, man in the middle attacks, spamming, and similar questionable acts)

4Any software not directly produced by the Flux Team

5Domains hosted by third parties (e.g.: Github, Gitlab, etc)

6Subdomains operated by third parties (e.g: info.zel.cash)

7Any Flux branded services operated by third parties