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 into finding bugs or exploits in Flux.
What can you earn?
All bugs will be evaluated according to the CVSS scoring scale and rewarded accordingly. The CVSS levels are:
How it works
You will receive rewards based on the severity of the issue found if you:
Make all possible effort to not interrupt or degrade our service.
Do not attempt to gain unauthorized access to user accounts, assets or information (use your own account/accounts to test against).
Do 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.
Do not exploit a security issue you discover beyond the point of validation on your own accounts/nodes.
Consent to be added to a list published of researchers who have submitted valid security reports.
However, should you wish to remain anonymous, we will respect your privacy. You must inform us at the time of submission, and we will not add your name to aforementioned list.
We 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.
Additionally, in order to qualify for rewards you must adhere to the following responsible disclosure policy:
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.
For website related issues: No data is removed from the website upon discovery.
The 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.
For 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.
Include an email for responses in your report.
Adhere to timeframes laid out in initial confirmation of report emails.
Please note that 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.
The following list is by no means exhaustive, so if you have a bug that is not on either the qualifying or non-qualifying lists, report it, it will be covered.
Injection flaws such as SQL, noSQL, Mongodb or OS injection that tricks command interpreter into executing unintended commands without proper authorization.
Broken authentication/session management that allows compromise of passwords, keys or session tokens.
Sensitive data exposure due to improper protection of data via insecure API or flaw in cryptography implementation.
Cross-Site Request Forgery (CSRF) for sensitive functions in a privileged context.
Remote Code Execution (RCE).
Insecure direct object references.
Any significant abuse-related methodologies that could lead to significant harm.
Non-original or previously disclosed/reported bugs (with fixes currently underway).
Non-technical attacks such as social engineering, phishing, or physical attacks against entities or infrastructure.
Any degrading/damaging the reliability or integrity of our services (such as DDoS attacks, man in the middle attacks, spamming, and similar questionable acts).
Any software not directly produced by the Flux team.
Domains hosted by third parties (e.g.: Github, Gitlab, etc).
Subdomains operated by third parties (e.g: info.runonflux.io).
Any Flux branded services operated by third parties.
How to report a bug
Send an email using the below PGP keys to [email protected] and no other email address. Failing to use the attached PGP keys for the bug report will invalidate any security issues higher than level 2 on the CVSS scale.
Process to follow
Write up a report on your findings.
PGP Encrypt the report with keys from URL.
Within 24 hours you will have an acknowledgement.
Adhere to timeline and additional information requests from the Flux team outlined in the acknowledgement email.
Discuss publication times and names.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: User-ID: Flux Security
Comment: Fingerprint: F3244FFC7207DB2CAA355DF506139DA3A0B13EC1
-----END PGP PUBLIC KEY BLOCK-----