mirror of
https://github.com/lingble/chatwoot.git
synced 2025-10-29 10:12:34 +00:00
57 lines
2.4 KiB
Markdown
57 lines
2.4 KiB
Markdown
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.
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
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.
|
|
|
|
If you have any questions about the process, contact security@chatwoot.com.
|
|
|
|
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.
|
|
|
|
> 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)
|
|
## Supported versions
|
|
|
|
| Version | Supported |
|
|
| ------- | -------------- |
|
|
| latest | ️✅ |
|
|
| <latest | ❌ |
|
|
|
|
|
|
## Vulnerabilities we care about 🫣
|
|
> Note: Please do not perform testing against Chatwoot production services. Use a `self-hosted instance` to perform tests.
|
|
- Remote command execution
|
|
- SQL Injection
|
|
- Authentication bypass
|
|
- Privilege Escalation
|
|
- Cross-site scripting (XSS)
|
|
- Performing limited admin actions without authorization
|
|
- CSRF
|
|
|
|
You can learn more about our triaging process [here](https://www.chatwoot.com/docs/contributing-guide/security-reports).
|
|
|
|
## Non-Qualifying Vulnerabilities
|
|
|
|
We consider the following out of scope, though there may be exceptions.
|
|
|
|
- Missing HTTP security headers
|
|
- Incomplete/Missing SPF/DKIM
|
|
- Reports from automated tools or scanners
|
|
- Theoretical attacks without proof of exploitability
|
|
- Social engineering
|
|
- Reflected file download
|
|
- Physical attacks
|
|
- Weak SSL/TLS/SSH algorithms or protocols
|
|
- 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).
|
|
- The user attacks themselves
|
|
- Incomplete/Missing SPF/DKIM
|
|
- Denial of Service attacks
|
|
- Brute force attacks
|
|
- DNSSEC
|
|
|
|
If you are unsure about the scope, please create a [report](https://github.com/chatwoot/chatwoot/security/advisories/new).
|
|
|
|
|
|
## Thanks
|
|
|
|
Thank you for keeping Chatwoot and our users safe. 🙇
|