| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
If you discover a security vulnerability in MatchCoreArena Client, please report it responsibly.
- DO NOT create a public GitHub issue
- DO email security concerns to: security@matchcorearena.com
- DO include the following information:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 1 week
- Resolution Timeline: Depends on severity
- Critical: 1-2 weeks
- High: 2-4 weeks
- Medium: 1-2 months
- Low: Next release
- Keep software updated: Always use the latest version
- Use strong passwords: For your MatchCoreArena account
- Enable 2FA: Use TOTP two-factor authentication
- Verify downloads: Only download from official sources
- Report suspicious activity: If you notice anything unusual
- Follow secure coding practices
- Validate all inputs
- Use parameterized queries (prevent SQL injection)
- Implement proper authentication
- Keep dependencies updated
- Review code for security issues
MatchCoreArena Client includes:
- Secure authentication: Email/password with TOTP support
- Token-based auth: JWT tokens with refresh mechanism
- Input validation: All user inputs are validated
- Secure storage: Sensitive data is stored securely
- HTTPS support: All communications can be encrypted
- Local storage: Some data is stored locally on the device
- Network communication: Ensure server uses HTTPS in production
- Third-party dependencies: Regularly updated for security patches
We currently do not have a formal bug bounty program, but we appreciate responsible disclosure and will acknowledge contributors in our release notes.
For security-related questions or concerns:
- Email: security@matchcorearena.com
- PGP Key: [Available upon request]
Thank you for helping keep MatchCoreArena Client secure!