| Version | Supported |
|---|---|
| 5.1.x | ✅ |
| 4.0.x | ✅ |
| < 4.0 | ❌ |
We take security seriously and appreciate your efforts to responsibly disclose your findings.
Do NOT open a public issue for security vulnerabilities. Instead, please report security issues through one of these channels:
- GitHub Security Advisories (Preferred): Report via GitHub
- Email: Send details to security@lanik.us
- Security Discussions: Open a discussion in our GitHub Discussions
- Security Issues: Create a Security Advisory on GitHub
When reporting a vulnerability, please include:
- Description: Clear explanation of the security issue
- Steps to Reproduce: Detailed steps to reproduce the vulnerability
- Impact Assessment: Potential impact and affected components
- Proof of Concept: If applicable, a minimal reproduction case
- Suggested Fix: If you have ideas for a fix (optional)
We are committed to responding to security reports in a timely manner:
- Initial Response: Within 48 hours of receiving the report
- Status Update: Within 5 business days with assessment
- Resolution: We will work diligently to fix critical vulnerabilities as quickly as possible
We ask that you:
- Give us reasonable time to investigate and fix the issue before public disclosure
- Do not access, modify, or delete user data
- Do not perform attacks that could harm the availability of our services
- Do not publicly disclose the vulnerability until we have had a chance to address it
This project provides a simple web service in a Docker container. Security considerations include:
- Container Security: All containers follow security best practices
- Web Service Security: Web service is configured with security hardening
- Input Validation: All inputs are validated to prevent injection attacks
- Use Latest Tags: Always use the latest stable tags
- Regular Updates: Keep your containers updated
- Security Scanning: Use security scanning tools on your images
When contributing to the project:
- Security Patches: Apply security patches promptly
- Code Review: Have security reviews for all changes
- Testing: Include security testing in CI/CD
For general security questions or concerns, you can:
- Open a discussion in our GitHub Discussions
- Contact the maintainers through the security email above for sensitive matters
Thank you for helping keep docker-web-service secure!