DO NOT CREATE PUBLIC ISSUES FOR SECURITY VULNERABILITIES
If you discover any security-related issues, please report them privately:
-
Email security advisories to:
gelir6714@gmail.com(not monitored by bots) -
Use GitHub Private Vulnerability Reporting (preferred):
Report vulnerability
- Project version and environment details
- Steps to reproduce the vulnerability
- Impact analysis and potential attack scenarios
- Any mitigation suggestions
- Your disclosure preferences
- Acknowledgement:
You'll receive confirmation of your report within 3 business days - Investigation:
Initial assessment within 7 days - Fix Development:
Patch development with regular updates - Release:
Coordinated release with CVE assignment - Public Disclosure:
After patch availability (typically 30-90 days post-fix)
- Remote code execution (RCE)
- Authentication bypasses
- Privilege escalation
- Sensitive data exposure
- Critical dependency vulnerabilities
- Supply chain compromises
- Theoretical vulnerabilities without PoC
- Self-XSS or low-impact CSRF
- Missing security headers without demonstrated impact
- Denial of Service (DoS) vulnerabilities
- Vulnerabilities in dependencies without known exploits
Security patches are released as:
- Immediate patch releases
- Security bulletins in GitHub Releases
- GitHub Security Advisories
- Always run Disware in a sandboxed environment
- Regularly update to the latest stable version