We actively support the following versions of StockMart with security updates:
| Version | Supported |
|---|---|
| latest | ✅ |
| < 1.0 | ❌ |
We take the security of StockMart seriously. If you discover a security vulnerability, please report it responsibly.
Please DO NOT report security vulnerabilities through public GitHub issues.
Instead, please report them through one of these channels:
-
GitHub Security Advisories (Preferred)
- Go to the Security Advisories page
- Click "Report a vulnerability"
- Fill out the form with details
-
Private Disclosure
- If you cannot use GitHub Security Advisories, contact the maintainers directly
- Include
[SECURITY]in your communication subject
Please include the following information in your report:
- Type of vulnerability (e.g., XSS, SQL injection, authentication bypass)
- Location - Full path to the affected source file(s)
- Configuration - Any special configuration required to reproduce
- Steps to reproduce - Detailed steps to reproduce the vulnerability
- Proof of concept - If possible, include code or screenshots
- Impact assessment - What an attacker could achieve by exploiting this
- Suggested fix - If you have recommendations for fixing the issue
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Resolution Target: Within 30 days for critical issues
- Acknowledgment: We will acknowledge your report within 48 hours
- Investigation: We will investigate and keep you informed of our progress
- Fix Development: We will work on a fix and may ask for your input
- Disclosure: We will coordinate disclosure timing with you
- Credit: We will credit you in our security advisories (unless you prefer anonymity)
When deploying StockMart, please follow these security guidelines:
- Always use strong passwords for admin accounts
- Enable rate limiting for login attempts
- Use HTTPS in production environments
- Never commit
.envfiles or credentials to version control - Use environment variables for sensitive configuration
- Rotate secrets and API keys regularly
- Deploy behind a reverse proxy (nginx, Caddy, etc.)
- Configure proper CORS settings for your domain
- Use firewall rules to restrict access to backend ports
- Use parameterized queries (already implemented in our Rust backend)
- Regular backups of game data
- Restrict database access to application servers only
- Validate all incoming WebSocket messages
- Implement connection limits per IP
- Use WSS (WebSocket Secure) in production
StockMart includes the following security features:
- Input Validation: All user inputs are validated on both client and server
- SQL Injection Prevention: Parameterized queries via SQLx
- XSS Protection: React's built-in XSS protection + Content Security Policy
- Rate Limiting: Configurable rate limits for API endpoints
- Session Management: Secure session handling with proper timeouts
- CORS Configuration: Strict CORS policies for API access
The following are in scope for security reports:
- StockMart backend (Rust)
- StockMart frontend (React/TypeScript)
- Trading engine and order matching
- Authentication and session management
- WebSocket communication
- Admin dashboard
The following are out of scope:
- Third-party dependencies (report to upstream maintainers)
- Issues in deployment infrastructure you manage
- Social engineering attacks
- Physical security
We maintain a list of security researchers who have responsibly disclosed vulnerabilities:
No vulnerabilities reported yet - be the first!
Thank you for helping keep StockMart and its users safe!