| Version | Supported |
|---|---|
| 1.1.x | ✅ |
| < 1.1 | ❌ |
DO NOT open public issues for security vulnerabilities.
Please report security vulnerabilities by emailing: richkmeli@gmail.com
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
-
Never use default credentials
- Change all passwords in
.envfile - Use strong, randomly generated passwords (min 16 characters)
- Change all passwords in
-
Encryption Key
- Generate a secure 32+ character encryption key
- Never commit encryption keys to version control
- Rotate keys periodically
-
Database Security
- Use separate database user with minimal privileges
- Enable SSL/TLS for database connections
- Regular backups with encryption
-
Network Security
- Use HTTPS only (configure SSL certificates)
- Implement firewall rules
- Use VPN or private networks when possible
-
Application Security
- Keep dependencies updated
- Enable security headers
- Implement rate limiting
- Regular security audits
Required environment variables for production:
DB_PASSWORD=<strong-password>
ENCRYPTION_KEY=<32-char-minimum-key>
SPRING_PROFILES_ACTIVE=prod
DEBUG_MODE=falseThis is a research/educational project demonstrating C2 infrastructure.
Use only in authorized, controlled environments.