| Version | Supported |
|---|---|
| 5.1.x | ✅ |
| 5.0.x | ✅ |
| 4.4.x | ✅ |
| < 4.4 | ❌ |
Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be in scope for the program. Common examples including:
- Cross-site scripting
- Cross-site request forgery
- Mixed-content scripts
- Authentication or authorization flaws
- Server-side code execution bugs
Out of concern for the availability of our services to all users, please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, brute force authentication, or do other similarly questionable things. We also discourage the use of any vulnerability testing tools that automatically generate very significant volumes of traffic.
Depending on their impacts, some of the reported issues may not qualify. Although we review them on a case-by-case basis, here are some of the issues that typically do not earn a monetary reward:
- Bugs requiring exceedingly unlikely user interaction Brute forcing
- User enumeration
- Non security related bugs
- Abuse
- When investigating a vulnerability, please, only ever target your own accounts. Never attempt to access anyone else's data and do not engage in any activity that would be disruptive or damaging to other users.
- In the case the same vulnerability is present on multiple products, please combine and send one report.
- If you have found a vulnerability, please contact us at security@emqx.io.
- Note that we are only able to answer technical vulnerability reports. Duplicate reports will not be rewarded, first report on the specific vulnerability will be rewarded.
- The report should include steps in plain text how to reproduce the vulnerability (not only video or images).