We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
If you discover a security vulnerability within MITI, please send an email to the maintainers. All security vulnerabilities will be promptly addressed.
Please do not report security vulnerabilities through public GitHub issues.
- Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- Confirmation of receipt within 48 hours
- A detailed response within 7 days
- Regular updates on the progress toward a fix
- Credit in the security advisory (unless you prefer to remain anonymous)
When using MITI:
- Use WSS (Secure WebSocket) in production environments
- Validate all input from ROS topics before processing
- Keep dependencies updated regularly
- Use environment variables for sensitive configuration
- Run with minimal privileges when deploying
- Monitor logs for suspicious activity
- WebSocket connections should be secured with WSS in production
- URDF files loaded from URLs should be from trusted sources only
- Browser localStorage is used for configuration - sensitive data should not be stored there