dnrops
/
open-webui
mirror of https://github.com/open-webui/open-webui
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
open-webui/docs/SECURITY.md

2.4 KiB
Raw Blame History

Security Policy

Our primary goal is to ensure the protection and confidentiality of sensitive data stored by users on open-webui.

Supported Versions

Version Supported
main ✅
others ❌

Reporting a Vulnerability

We appreciate the community's interest in identifying potential vulnerabilities. However, effective immediately, we will not accept low-effort vulnerability reports. To ensure that submissions are constructive and actionable, please adhere to the following guidelines:

  1. No Vague Reports: Submissions such as "I found a vulnerability" without any details will be treated as spam and will not be accepted.

  2. In-Depth Understanding Required: Reports must reflect a clear understanding of the codebase and provide specific details about the vulnerability, including the affected components and potential impacts.

  3. Proof of Concept (PoC) is Mandatory: Each submission must include a well-documented proof of concept (PoC) that demonstrates the vulnerability. If confidentiality is a concern, reporters are encouraged to create a private fork of the repository and share access with the maintainers. Reports lacking valid evidence will be disregarded.

  4. Required Patch Submission: Along with the PoC, reporters must provide a patch or actionable steps to remediate the identified vulnerability. This helps us evaluate and implement fixes rapidly.

  5. Streamlined Merging Process: When vulnerability reports meet the above criteria, we can consider them for immediate merging, similar to regular pull requests. Well-structured and thorough submissions will expedite the process of enhancing our security.

Submissions that do not meet these criteria will be closed, and repeat offenders may face a ban from future submissions. We aim to create a respectful and constructive reporting environment, where high-quality submissions foster better security for everyone.

Product Security

We regularly audit our internal processes and system architecture for vulnerabilities using a combination of automated and manual testing techniques. We are also planning to implement SAST and SCA scans in our project soon.

For immediate concerns or detailed reports that meet our guidelines, please create an issue in our issue tracker or contact us on Discord.

Last updated on 2024-08-06.