|
1 |
| -# Security Policy |
2 |
| -Chatwoot is looking forward to working with security researchers across the world to keep Chatwoot and our users safe. If you have found an issue in our systems/applications, please reach out to us. |
| 1 | +Chatwoot is looking forward to working with security researchers worldwide to keep Chatwoot and our users safe. If you have found an issue in our systems/applications, please reach out to us. |
3 | 2 |
|
4 | 3 | ## Reporting a Vulnerability
|
5 | 4 |
|
6 |
| -We use [huntr.dev](https://huntr.dev/) for security issues that affect our project. If you believe you have found a vulnerability, please disclose it via this [form](https://huntr.dev/bounties/disclose). |
| 5 | +We use Github to track the security issues that affect our project. If you believe you have found a vulnerability, please disclose it via this [form](https://github.com/chatwoot/chatwoot/security/advisories/new). This will enable us to review the vulnerability, fix it promptly, and reward you for your efforts. |
7 | 6 |
|
8 |
| -This will enable us to review the vulnerability, fix it promptly, and reward you for your efforts. |
| 7 | +If you have any questions about the process, contact [email protected]. |
9 | 8 |
|
10 |
| -If you have any questions about the process, feel free to reach out to [email protected]. |
| 9 | +Please try your best to describe a clear and realistic impact for your report, and please don't open any public issues on GitHub or social media; we're doing our best to respond through Github as quickly as possible. |
11 | 10 |
|
| 11 | +> Note: Please use the email for questions related to the process. Disclosures should be done via [Github](https://github.com/chatwoot/chatwoot/security/advisories/new) |
| 12 | +## Supported versions |
12 | 13 |
|
13 |
| -## Out of scope |
| 14 | +| Version | Supported | |
| 15 | +| ------- | -------------- | |
| 16 | +| latest | οΈβ
| |
| 17 | +| <latest | β | |
14 | 18 |
|
15 |
| -Please do not perform testing against Chatwoot production services. Use a self hosted instance to perform tests. |
16 | 19 |
|
17 |
| -We consider the following to be out of scope, though there may be exceptions. |
| 20 | +## Vulnerabilities we care about π«£ |
| 21 | +> Note: Please do not perform testing against Chatwoot production services. Use a `self-hosted instance` to perform tests. |
| 22 | +- Remote command execution |
| 23 | +- SQL Injection |
| 24 | +- Authentication bypass |
| 25 | +- Privilege Escalation |
| 26 | +- Cross-site scripting (XSS) |
| 27 | +- Performing limited admin actions without authorization |
| 28 | +- CSRF |
| 29 | + |
| 30 | +You can learn more about our triaging process [here](https://www.chatwoot.com/docs/contributing-guide/security-reports). |
| 31 | + |
| 32 | +## Non-Qualifying Vulnerabilities |
| 33 | + |
| 34 | +We consider the following out of scope, though there may be exceptions. |
18 | 35 |
|
19 | 36 | - Missing HTTP security headers
|
20 |
| -- Self XSS |
21 |
| -- HTTP Host Header XSS without working proof-of-concept |
| 37 | +- Incomplete/Missing SPF/DKIM |
| 38 | +- Reports from automated tools or scanners |
| 39 | +- Theoretical attacks without proof of exploitability |
| 40 | +- Social engineering |
| 41 | +- Reflected file download |
| 42 | +- Physical attacks |
| 43 | +- Weak SSL/TLS/SSH algorithms or protocols |
| 44 | +- Attacks involving physical access to a user's device or a device or network that's already seriously compromised (e.g., man-in-the-middle). |
| 45 | +- The user attacks themselves |
22 | 46 | - Incomplete/Missing SPF/DKIM
|
23 | 47 | - Denial of Service attacks
|
| 48 | +- Brute force attacks |
24 | 49 | - DNSSEC
|
25 |
| -- Social Engineering attacks |
26 | 50 |
|
27 |
| -If you are not sure about the scope, please create a report. |
| 51 | +If you are unsure about the scope, please create a [report](https://github.com/chatwoot/chatwoot/security/advisories/new). |
| 52 | + |
28 | 53 |
|
29 | 54 | ## Thanks
|
30 | 55 |
|
31 |
| -Thank you for keeping Chatwoot and our users safe. π |
| 56 | +Thank you for keeping Chatwoot and our users safe. π |
0 commit comments